[shrinkwrap-issues] [JBoss JIRA] (SHRINKDESC-163) Deal with descriptors with multiple possible roots better

[Ralf Battenfeld (JIRA)]

    [ https://issues.jboss.org/browse/SHRINKDESC-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117202#comment-13117202 ] 

Ralf Battenfeld commented on SHRINKDESC-163:
--------------------------------------------

I was checking some other possibilities but at the end, if believe the only 'real' solution is that we support multi root elements in a descriptor. If you all agree then I will work on this. It will take a little time to implement it.

This solution will then replace the three module descriptors by one descriptor. You then can load an XML file and navigate through the top level methods in order to find which flavor of the module.xml you have loaded.

Does that make sense?

> Deal with descriptors with multiple possible roots better
> ---------------------------------------------------------
>
>                 Key: SHRINKDESC-163
>                 URL: https://issues.jboss.org/browse/SHRINKDESC-163
>             Project: ShrinkWrap Descriptors
>          Issue Type: Feature Request
>    Affects Versions: 2.0.0-alpha-8
>            Reporter: Toby Crawley
>
> When implementing SHRINKDESC-162, I created three different
> descriptors for module.xml ({{ModuleDescriptor}},
> {{ModuleAliasDescriptor}}, {{ModuleAbsentDescriptor}}) corresponding to
> the three root elements listed in the xsd ({{module}}, {{module-alias}},
> {{module-absent}}). This works fine if you are generating a module.xml,
> but if you are loading in an existing file, you don't know without
> looking at the file contents to know which type to instantiate.
> It would be swell if there was a way for descriptors to support
> multiple roots and do the correct thing. Or does that already exist
> and I missed it?



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)