[jboss-jira] [JBoss JIRA] Commented: (JBMICROCONT-446) bean-deployer xsds don't contain web references

[Wolfgang Knauf (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBMICROCONT-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12474607#action_12474607 ] 

Wolfgang Knauf commented on JBMICROCONT-446:
--------------------------------------------

Hi David,

after doing a bit of google, I agree with you: it seems that the parser should search for the included file in the same location as the current XSD if no full URI is specified.
A short test reveals: this seems to work for jboss_5_1.xsd and jboss-common_5_1.xsd.

The only possible problem where this might fail is when you add "bean-deployer_2_0.xsd" to your project and don't add the included "jboss-beans-common_2_0.xsd". Then Eclipse cannot find the included XSD (a similar thing happened to me some time ago while checking another validation error in jboss_5_1.xsd). 

Hopefully, the XSD files will be added to the JBoss website so that I can give them a try.

So, if you don't want to change it, you can close this issue. But I would prefer full web URIs ;-).

> bean-deployer xsds don't contain web references
> -----------------------------------------------
>
>                 Key: JBMICROCONT-446
>                 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-446
>             Project: JBoss Microcontainer
>          Issue Type: Bug
>            Reporter: Wolfgang Knauf
>            Assignee: Kabir Khan
>
> bean-deployer_2_0.xsd:
>    <xsd:redefine schemaLocation="jboss-beans-common_2_0.xsd">
> =>should point. 
>    <xsd:redefine schemaLocation="http://www.jboss.org/j2ee/schema/jboss-beans-common_2_0.xsd">
> The comment for a sample instance should also contain a schema location attribute:
>          <deployment xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>             xmlns="urn:jboss:bean-deployer:2.0"
>             xsi:schemaLocation="urn:jboss:bean-deployer:2.0 http://www.jboss.org/j2ee/schema/bean-deployer_2_0.xsd">
> ==================
> bean-deployer_1_0.xsd:
> The comment for a sample instance should point to the web schema location:
>          <deployment
>             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>             xsi:schemaLocation="urn:jboss:bean-deployer http://www.jboss.org/j2ee/schema/bean-deployer_1_0.xsd"
>             xmlns="urn:jboss:bean-deployer">
> =================
> policy_1_0.xsd:
>    <xsd:import namespace="urn:jboss:bean-deployer:2.0"/>
> should be:
>    <xsd:import namespace="urn:jboss:bean-deployer:2.0" schemaLocation="http://www.jboss.org/j2ee/schema/bean-deployer_1_0.xsd"/>
> =================
> bean-deployer_2_0.xsd raises validation errors in Eclipse:
> -rcase-RecurseLax.2: There is not a complete functional mapping between the particles.	
> -src-redefine.6.2.2: Group 'valueGroup' does not properly restrict the group it redefines; constraint violated:  'rcase-RecurseLax.2'.
> According to the forum (http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4187426 ), this might also be a bug of the validator, but I don't have enough xsd knowledge to create a Xerces bugreport.

-- 
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