[
https://issues.jboss.org/browse/WFCORE-516?page=com.atlassian.jira.plugin...
]
Rob Stryker commented on WFCORE-516:
------------------------------------
While AS7-1345 fixed the issue in version 1,.1 of the schema, the fact is that several
example projects are still using the 1.0 schema file in their various descriptors. We
can't force the example projects to update, and even if we could, it would make those
example projects no longer valid for older versions of wildfly.
Assuming there's no issue with changing this (ie backwards compatability), I think it
should still be fixed in the 1.0 version of the schema.
If there *is* an issue with the schema, then there's not much we can do aside from try
to strong-arm the various example projects to use the newer schema.
We in JBoss Tools could also just update our copy of the schema, but this would make it
no longer match the official version and I think that's the wrong path to go.
jboss-deployment-structure-1_0.xsd Error: 'Attribute name is not
allowed to appear in element 'sub-deployment'
--------------------------------------------------------------------------------------------------------------
Key: WFCORE-516
URL:
https://issues.jboss.org/browse/WFCORE-516
Project: WildFly Core
Issue Type: Bug
Components: Modules
Reporter: Rob Stryker
Assignee: David Lloyd
When the projects
mail-ear from the Seam example mail [1]
tasks-ear from the Seam example tasks [2]
are imported into JBDS the error
Attribute 'name' is not allowed to appear in element 'sub-deployment'
will be shown for the file jboss-deployment-structure.xml.
It is caused by the bug in jboss-deployment-structure-1_0.xsd; see AS7-1345
This bug should be IMHO ignored and the error shouldn't be shown.
[1]
https://github.com/seam2/jboss-seam/tree/Seam_2_3/examples/mail
[2]
https://github.com/seam2/jboss-seam/tree/Seam_2_3/examples/tasks
https://github.com/wildfly/wildfly-core/pull/442/files
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)