[jboss-jira] [JBoss JIRA] (AS7-5943) StandardConfigsXMLValidationUnitTestCase cannot find jboss-common_6_0.xsd on IBM JDK

[Ivo Studensky (JIRA)]

    [ https://issues.jboss.org/browse/AS7-5943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734181#comment-12734181 ] 

Ivo Studensky edited comment on AS7-5943 at 11/14/12 10:16 AM:
---------------------------------------------------------------

The issue can be easily fixed by adding the following line to AbstractValidationUnitTest. It might also be a configuration issue of IBM JDK though.

{code}
NAMESPACE_MAP.put("http://www.jboss.org/j2ee/schema/jboss-common_6_0.xsd", "jboss-common_6_0.xsd");
{code}
                
      was (Author: istudens):
    The issue can be easily fixed by adding of the following line to AbstractValidationUnitTest.

{code}
NAMESPACE_MAP.put("http://www.jboss.org/j2ee/schema/jboss-common_6_0.xsd", "jboss-common_6_0.xsd");
{code}
                  
> StandardConfigsXMLValidationUnitTestCase cannot find jboss-common_6_0.xsd on IBM JDK
> ------------------------------------------------------------------------------------
>
>                 Key: AS7-5943
>                 URL: https://issues.jboss.org/browse/AS7-5943
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Test Suite
>    Affects Versions: 7.1.3.Final (EAP), 7.2.0.Alpha1
>         Environment: IBM JDK
> IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr9-20110203_74623 (JIT enabled, AOT enabled)
> IBM J9 VM (build 2.6, JRE 1.7.0 Linux amd64-64 20120809_118929 (JIT enabled, AOT enabled)
>            Reporter: Ivo Studensky
>            Assignee: Ivo Studensky
>
> StandardConfigsXMLValidationUnitTestCase fails on IBM JDK since it cannot find jboss-common_6_0.xsd schema, see the snippet below for more details. The failure is triggered by invocation of StandardConfigsXMLValidationUnitTestCase#DEFAULT_RESOURCE_RESOLVER.resolveResource() method with systemId == 'http://www.jboss.org/j2ee/schema/jboss-common_6_0.xsd' which is missing in a NAMESPACE_MAP field. Furthermore, compared to Oracle JDK the resolveResource method is invoked with different parameters on IBM JDK, i.e. it loads different XSD's into the validation of the same XML files. On Oracle JDK it is never asked for jboss-common systemId. That is weird.
> {noformat}
> junit.framework.AssertionFailedError: http://www.jboss.org/j2ee/schema/jboss-common_6_0.xsd not found
> 	at junit.framework.Assert.fail(Assert.java:50)
> 	at junit.framework.Assert.assertTrue(Assert.java:20)
> 	at junit.framework.Assert.assertNotNull(Assert.java:218)
> 	at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest.discoverXsd(AbstractValidationUnitTest.java:208)
> 	at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$2.resolveResource(AbstractValidationUnitTest.java:124)
> 	at org.apache.xerces.util.DOMEntityResolverWrapper.resolveEntity(Unknown Source)
> 	at org.apache.xerces.impl.XMLEntityManager.resolveEntity(Unknown Source)
> 	at org.apache.xerces.impl.xs.XMLSchemaLoader.resolveDocument(Unknown Source)
> 	at org.apache.xerces.impl.xs.traversers.XSDHandler.resolveSchema(Unknown Source)
> 	at org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown Source)
> 	at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown Source)
> 	at org.apache.xerces.impl.xs.XMLSchemaLoader.loadSchema(Unknown Source)
> 	at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(Unknown Source)
> 	at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(Unknown Source)
> 	at org.apache.xerces.jaxp.validation.XMLSchemaFactory.newSchema(Unknown Source)
> 	at org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.parseXml(StandardConfigsXMLValidationUnitTestCase.java:150)
> 	at org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testHostSlave(StandardConfigsXMLValidationUnitTestCase.java:82)
> {noformat}

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