Message: The following issue has been re-assigned.
Assignee: Michael Glavassevich (mailto:[EMAIL PROTECTED]) --------------------------------------------------------------------- View the issue: http://issues.apache.org/jira/browse/XERCESJ-843 Here is an overview of the issue: --------------------------------------------------------------------- Key: XERCESJ-843 Summary: XInclude bug on included xml that its own schema and no DTD Type: Bug Status: Open Priority: Blocker Project: Xerces2-J Components: XInclude 1.0 Versions: 2.6.0 Assignee: Michael Glavassevich Reporter: Don Bate Created: Tue, 25 Nov 2003 9:40 PM Updated: Fri, 11 Jun 2004 2:07 PM Environment: Operating System: MacOS X Platform: Macintosh Description: I get the following error message under both the 2.5.0 and 2.6.0 releases using XInclude. The included file (pmtext) has its own schema in its own namespace but no DTD. The including file also has its own schema and no DTD. The including file's schema imports the included file's schema. ================== LowLevelErrorHandler: error domain=[http://www.w3.org/TR/1998/REC-xml-19980210] key=[MSG_GRAMMAR_NOT_FOUND] ::urn:com:streamvantage:pmtext:urn:com:streamvantage:pmtext:urn:com:streamvantage:pmtext:3:19:Document is invalid: no grammar found. ================== ================== LowLevelErrorHandler: error domain=[http://www.w3.org/TR/1998/REC-xml-19980210] key=[RootElementTypeMustMatchDoctypedecl] ::urn:com:streamvantage:pmtext:urn:com:streamvantage:pmtext:urn:com:streamvantage:pmtext:3:19:Document root element "pm:pmDescriptions", must match DOCTYPE root "null". ================== I ran it under a debugger and the messages are generated in XMLNSDocumentScannerImpl.scanStartElement() at the start of the included file. fPerformValidation is false for the including document but becomes true for the included document. My guess is that somehow the DTD validator is turned back on. Under 2.5.0, I simply commented out the fPerformValidation check and everything worked correctly. However, under 2.6.0 I get a null pointer exception at the following because parentBaseURI is null: ava.lang.NullPointerException at org.apache.xerces.xinclude.XIncludeHandler.sameBaseURIAsIncludeParent(XIncludeHandler.java:1299) at org.apache.xerces.xinclude.XIncludeHandler.processAttributes(XIncludeHandler.java:1377) at org.apache.xerces.xinclude.XIncludeHandler.startElement(XIncludeHandler.java:621) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:321) at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(XMLNSDocumentScannerImpl.java:617) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentS%239B119.java:1617) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentS%239B119.java:338) at org.apache.xerces.parsers.XML11Configuration.parse(XML11Configuration.java:827) at org.apache.xerces.parsers.XML11Configuration.parse(XML11Configuration.java:757) at org.apache.xerces.xinclude.XIncludeHandler.handleIncludeElement(XIncludeHandler.java:1173) at org.apache.xerces.xinclude.XIncludeHandler.emptyElement(XIncludeHandler.java:638) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:313) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentS%239B119.java:1549) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentS%239B119.java:338) at org.apache.xerces.parsers.XML11Configuration.parse(XML11Configuration.java:827) at org.apache.xerces.parsers.XML11Configuration.parse(XML11Configuration.java:757) at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:148) at com.streamvantage.BaseUtilities.Alarm.parseAlarmDescriptions(Alarm.java:111) at com.streamvantage.BaseUtilities.Alarm.initialize(Alarm.java:68) at Test.main(Test.java:10) --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
