You are viewing a plain text version of this content. The canonical link for it is here.

Posted to j-dev@xerces.apache.org by bu...@apache.org on 2004/01/09 21:51:54 UTC

DO NOT REPLY [Bug 26028] - setEntityResolver doesn't set resolver in Entity Manager

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=26028>.
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=26028

setEntityResolver doesn't set resolver in Entity Manager

mrglavas@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID
            Summary|setEntityResolver doesn't   |setEntityResolver doesn't
                   |set resolver in Entity      |set resolver in Entity
                   |Manager                     |Manager



------- Additional Comments From mrglavas@apache.org  2004-01-09 20:51 -------
The problem is your encountering is with the SAX API not Xerces. If you have a 
look at the source code for (org.xml.sax.helpers.XMLFilterImpl) [1] you'll see 
that setting an entity resolver (see setEntityResolver) on the filter doesn't 
set it on the underlying parser so it's never propogated to Xerces' SAX parser.

I remember a few other people have run into this problem in the past. If you're 
interested in having this fixed, trying opening a bug report in the SAX 
community [2].

[1] 
http://cvs.sourceforge.net/viewcvs.py/sax/sax2/src/org/xml/sax/helpers/XMLFilter
Impl.java?annotate=1.3.2.7
[2] http://www.saxproject.org

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