[
https://issues.jboss.org/browse/SHRINKDESC-163?page=com.atlassian.jira.pl...
]
Ralf Battenfeld commented on SHRINKDESC-163:
--------------------------------------------
Hmm, I see the three root elements.
I am right, your problem is that you have first to analyze the file content in order to
find out which of the three module descriptors is the right one? If yes, how does the
wildfly implementation tackle this problem?
For me, it looks that this is more a modeling issue, I mean, the module.xsd could have one
root element and three nested elements as choices for example.
But besides this, I will think what we can do from the descriptor implementation side. The
module.xsd will not be changed just because of this JIRA:-)
I will have some time over the weekend.
Regards,
Ralf
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)