DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11787>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11787 Xerces try to resolve a publicId=systemId=null Summary: Xerces try to resolve a publicId=systemId=null Product: Xerces2-J Version: 2.0.1 Platform: All OS/Version: All Status: NEW Severity: Major Priority: Other Component: SAX AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Overview Description: Implementing XML schema in the jakarta-tomcat-5 projet, I get the following error when I'm trying to resolve locally a DTD. I might not be related to schema validation. The exception occurs because the resolveEntity method (we are using SAX) got the following value: publicId=null systemId=null .. and I'm trying to return null (what can I do with both value = null?) It produces: Exception ---------- SEVERE: Parse Warning at line 10 column 14: schema_reference.4: Failed to read schema doc ument 'null', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'null', because 1) could not find the document; 2) the document could not be read; 3) the root e lement of the document is not <xsd:schema>. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandle rWrapper.java:232) at org.apache.xerces.util.ErrorHandlerWrapper.warning(ErrorHandlerWrapper.java:14 1) at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:358) at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:296) at org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaWarning(XSDHandler .java:1841) at org.apache.xerces.impl.xs.traversers.XSDHandler.getSchema(XSDHandler.java:1298 ) at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(XSDHandler.java:39 2) at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(XSDHandler.java:38 1) at org.apache.xerces.impl.xs.XMLSchemaValidator.parseSchema(XMLSchemaValidator.ja va:2250) at org.apache.xerces.impl.xs.XMLSchemaValidator.findSchemaGrammar(XMLSchemaValida tor.java:2178) at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValid ator.java:1724) at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.j ava:568) at org.apache.xerces.impl.XMLNamespaceBinder.handleStartElement(XMLNamespaceBinde r.java:832) at org.apache.xerces.impl.XMLNamespaceBinder.startElement(XMLNamespaceBinder.java :568) at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(XMLDTDValidator.java:7 96) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocu mentFragmentScannerImpl.java:752) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatche r.dispatch(XMLDocumentFragmentScannerImpl.java:1454) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocument FragmentScannerImpl.java:333) at org.apache.xerces.parsers.StandardParserConfiguration.parse(StandardParserConf iguration.java:529) at org.apache.xerces.parsers.StandardParserConfiguration.parse(StandardParserConf ***** NOTE: the bug does not occurs when I build the xml-xerces reposity (081602) **** Steps to Reproduce: Attached is a test.bat file that contains the logic to reproduce the problem. You need the follwing jakarta project (jar) in order to reproduce the bug: - jakarta-commons/digester-1.3 - jakarta-commons/collections-2.0 - jakarta-commons/logging-1.0.1 - jakarta-servlet-api-5 Just cvs the workspace and do an "ant dist" in each repository. the test.bat file gives you an overview on how to start the test case: XMLSchemaTest.java Actual Results: Looping over and over *** NOTE **** Where can I put the test case? Email-me for more info. *** IMPORTANT ****************************************************** The bug do not occur when using the current xml-xerces workspace * Xerces 2.0.2 produces a StackTraceOverflow :-( * ******************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
