[jboss-jira] [JBoss JIRA] Closed: (JBMETA-200) Validation errors in jboss_5_1.xsd

Alexey Loubyansky (JIRA) jira-events at lists.jboss.org
Thu May 14 04:15:47 EDT 2009


     [ https://jira.jboss.org/jira/browse/JBMETA-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Loubyansky closed JBMETA-200.
------------------------------------

    Fix Version/s: 1.0.1.GA
       Resolution: Done


Fixed. Thanks a lot. We should add XSD validation tests.

> Validation errors in jboss_5_1.xsd
> ----------------------------------
>
>                 Key: JBMETA-200
>                 URL: https://jira.jboss.org/jira/browse/JBMETA-200
>             Project: JBoss Metadata
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.0.0.CR17
>         Environment: Eclipse 3.4, WebToolsPlatform 3.0
>            Reporter: Wolfgang Knauf
>            Assignee: Alexey Loubyansky
>            Priority: Critical
>             Fix For: 1.0.1.GA
>
>
> 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/resources/schema/jboss-common_5_1.xsd) 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

        



More information about the jboss-jira mailing list