xerces-j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From xerces-j-...@xml.apache.org
Subject [jira] Resolved: (XERCESJ-862) setEntityResolver doesn't set resolver for filter chains of xsls
Date Wed, 22 Sep 2004 04:40:38 GMT

   The following issue has been resolved as FIXED.

   Resolver: Michael Glavassevich
       Date: Tue, 21 Sep 2004 9:39 PM

No activity on this report in over 8 months. Given the observations of the reporter it seems
highly likely that this is a problem with the XMLFilter implementation and not Xerces, so
resolving this report.
View the issue:

Here is an overview of the issue:
        Key: XERCESJ-862
    Summary: setEntityResolver doesn't set resolver for filter chains of xsls
       Type: Bug

     Status: Resolved
 Resolution: FIXED

    Project: Xerces2-J

   Reporter: Walt Fitzharris

    Created: Fri, 9 Jan 2004 8:42 PM
    Updated: Tue, 21 Sep 2004 9:39 PM
Environment: Operating System: Windows NT/2K
Platform: PC

If I create an XMLReader in a simple scenario with a contenthandler, it 
respects the entity resolver that I set with setEntityResolver.

Take that same reader and put it at the head of a SAX filter chain: presto! the 
reader ignores the custom entity resolver and tries to find entities in the 
default manner...not good.

All I want to do is configure the Entity Manager (I'm using JAXP) such that it 
will know what resolver to use.  I am making an assumption here that this is a 
bug -- that when a reader is in a filter chain context, that a call to 
setEntityResolver does not end up setting the resolver property for the entity 

Here's the stack trace I get...the reason the DTD is not found is that it is 
not in the directory where the program is run...the custom resolver is supposed 
to tell the parser where the DTD is...

java.io.FileNotFoundException: X:\ce_xml\xeldm\infra\formatter\Courtcase-V2-
norm.dtd (The system cannot find the file specified)
	at java.io.FileInputStream.open(Native Method)
	at java.io.FileInputStream.<init>(FileInputStream.java:103)
	at java.io.FileInputStream.<init>(FileInputStream.java:66)
	at sun.net.www.protocol.file.FileURLConnection.connect
	at sun.net.www.protocol.file.FileURLConnection.getInputStream
	at java.net.URL.openStream(URL.java:960)
	at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source)
	at org.apache.xerces.impl.XMLEntityManager.startDTDEntity(Unknown 
	at org.apache.xerces.impl.XMLDTDScannerImpl.setInputSource(Unknown 
	at org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch
(Unknown Source)
	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument
(Unknown Source)
	at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
	at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
	at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
	at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
	at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
	at com.lxnx.fab.ce.xeldm.infra.FormatterSAXFilterMain.main
Exception in thread "main"

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org

View raw message