[
https://issues.jboss.org/browse/WFLY-2851?page=com.atlassian.jira.plugin....
]
Harald Wellmann updated WFLY-2851:
----------------------------------
Description:
The following deployment structure cannot be validated against the XML schema:
{code:xml}
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
<deployment>
<dependencies>
<module name="foo"/>
</dependencies>
</deployment>
</jboss-deployment-structure>
{code}
This looks like a glitch in the schema where the {{module-alias}} element in
{{deploymentType}} is missing a {{minOccurs="0"}}.
The same holds for the {{filter}} element of {{resource-root}}, which should be optional
according to the schema documentation.
was:
The following deployment structure cannot be validated against the XML schema:
{code:xml}
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
<deployment>
<dependencies>
<module name="foo"/>
</dependencies>
</deployment>
</jboss-deployment-structure>
{code}
This looks like a glitch in the schema where the {{module-alias}} element in
{{deploymentType}} is missing a {{minOccurs="0"}}.
Can't validate jboss-deployment-structure.xml due to incorrect
schema
---------------------------------------------------------------------
Key: WFLY-2851
URL:
https://issues.jboss.org/browse/WFLY-2851
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 8.0.0.CR1
Reporter: Harald Wellmann
The following deployment structure cannot be validated against the XML schema:
{code:xml}
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
<deployment>
<dependencies>
<module name="foo"/>
</dependencies>
</deployment>
</jboss-deployment-structure>
{code}
This looks like a glitch in the schema where the {{module-alias}} element in
{{deploymentType}} is missing a {{minOccurs="0"}}.
The same holds for the {{filter}} element of {{resource-root}}, which should be optional
according to the schema documentation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira