[ https://jira.jboss.org/jira/browse/JBMETA-204?page=com.atlassian.jira.plu... ] Zachary Bedell updated JBMETA-204: ---------------------------------- Summary: Validation errors in jboss_5_1.xsd (missing webservice-descriptionType) (was: Validation errors in jboss_5_1.xsd) Fix Version/s: (was: 1.0.1.GA) Affects Version/s: 1.0.1.GA (was: 1.0.0.CR17) Description: An additional validation issue with current trunk jboss_5_1.xsd. The webservicesType complex type references type jboss:webservice-descriptionType which is missing. Copying the type from the jboss_5_0.xsd (which appears directly the webservicesType object around line 1223) resolves the issue. (was: I tried to create a jboss.xml from jboss_5_1.xsd, using Eclipe/WebTools for validation. To achieve this, I picked newest "jboss_5_1.xsd" and "jboss_common_5_1.xsd" from trunk (http://fisheye.jboss.org/browse/JBossAS/projects/metadata/trunk/src/main/...) and added them to an eclipse web project. The files at http://www.jboss.org/j2ee/schema/ are much older and with more problems... This results in several problems: ================= Import of "javaee_5.xsd" in jboss_common_5_1.xsd does not point to the web location: <xsd:import namespace="http://java.sun.com/xml/ns/javaee" schemaLocation="javaee_5.xsd"/> It should be: <xsd:import namespace="http://java.sun.com/xml/ns/javaee" schemaLocation="http://java.sun.com/xml/ns/javaee/javaee_5.xsd"... ================= Next one is in "jboss_5_1.xsd" cos-nonambig: "http://www.jboss.com/xml/ns/javaee":security-identity and "http://www.jboss.com/xml/ns/javaee":security-identity (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles. jboss_5_1.xsd Reason: Element "security-identity" in "message-driven-beanType" is duplicate. Same issue was resolved for jboss_5_0.xsd: https://jira.jboss.org/jira/browse/JBMETA-185 ================= jboss_5_1.xsd contains this imports: <xsd:include schemaLocation="jboss-common_5_1.xsd"/> It must point to a valid url: http://www.jboss.org/j2ee/schema/jboss-common_5_1.xsd ================ And finally: the usage comment talk about "5.0" and "jboss_5_0.xsd", should be 5.1 ) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMETA-204?page=com.atlassian.jira.plu... ] Alexey Loubyansky commented on JBMETA-204: ------------------------------------------ The online versions of the schemas are out of date. This is one contains webservice-descriptionType http://anonsvn.jboss.org/repos/jbossas/projects/metadata/trunk/src/main/r... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMETA-204?page=com.atlassian.jira.plu... ] Alexey Loubyansky commented on JBMETA-204: ------------------------------------------ This is what JBoss AS does. All DTDs and XSDs are resolved locally. Implementation of EntityResolver is responsible for that. Here is http://anonsvn.jboss.org/repos/common/common-core/trunk/src/main/java/org... as an example. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMETA-204?page=com.atlassian.jira.plu... ] Alexey Loubyansky commented on JBMETA-204: ------------------------------------------ 5_1 schemas are considered production ready. The error posted means schema binding was not resolved as it should have been, i.e. instead of using schema binding based on Java JAXB/JBossXB annotations, the schema binding was built by parsing XSD which won't work. Perhaps this is related to your attempts to modify schemaLocations and the resolution process. Let's use user forums to continue since so far it's only a discussion. (Add the forum thread URL to this issue so I don't miss it) Thanks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira