Open starksm64 opened 2 weeks ago
The usecase seems to be to navigate from a container to the default protocol for example, but this could be done via just parent/child relationships. I don't see that all methods are usable from a given point in the descriptor graph, but maybe I am missing something.
I'd agree this doesn't make much sense. I don't really know the reason, but my guess would be because the return type for each method on the interface is a ApplicationDescriptor
so the implementations could just return this
.
Yes, I guess it was an attempt at a fluid API, but it is not logical. I guess we need a proper proposal to update the interface and think about supporting other descriptor formats.
Issue Overview
Looking at the org.jboss.arquillian.config.descriptor.api.ArquillianDescriptor interface:
I see that every single interface type returned by the methods also extend the ArquillianDescriptor:
I can't understand what the purpose is or how it could effectively be used.
Expected Behaviour
I would expect each type to only extend the org.jboss.shrinkwrap.descriptor.api.Descriptor
Current Behaviour
Seems recursive for no practical reason.