[jboss-jira] [JBoss JIRA] Resolved: (JBAS-4899) Failed to resolve schema nsURI= location=null

Scott M Stark (JIRA) jira-events at lists.jboss.org
Thu Oct 25 01:14:01 EDT 2007


     [ http://jira.jboss.com/jira/browse/JBAS-4899?page=all ]

Scott M Stark resolved JBAS-4899.
---------------------------------

    Resolution: Done

The latest jbossxb snapshot (rev 1654) will pass in the root element local name as the schemaLocation if no other schemaLocation could be found. This allows one to map the root element name to a binding class as jbossas does in its metadata-beans.xml:

   <bean name="SchemaResolverConfig"
      class="org.jboss.xb.binding.sunday.unmarshalling.SchemaResolverConfig">
      <!-- schemaLocation to JBossXBuilder binding classes -->
      <property name="bindingClassesByLocations">
         <map keyClass="java.lang.String" valueClass="java.lang.String">
            <entry>
               <key>jboss</key>
               <value>org.jboss.metadata.ejb.jboss.JBoss50DTDMetaData</value>
            </entry>            
...


> Failed to resolve schema nsURI= location=null
> ---------------------------------------------
>
>                 Key: JBAS-4899
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4899
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> This happens when <jboss-web> does not contain a doctype declaration. This is more a backward compatibility issue.
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=null
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:306)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list