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 for filter chains of xsls ------- Additional Comments From [EMAIL PROTECTED] 2004-01-12 17:09 ------- Based on your comment I still think this must be a problem with the filter (which is being created by an XSLT processor). See the (ASCII) diagrams at the bottom. Scenario 1, where you've registered a handler on the SAX parser is working. A SAX filter works by consuming the events from the parser (as a handler), doing some processing on them, and then forwarding those events to its own handler. The direction of communication is the other way when registering handlers, setting feature and properties and invoking the parse. See Scenario 2. The filter is in the position of your application code (which invokes the parser) and handler. I believe the filter isn't registering your entity resolver on the parser and/or it isn't calling resolveEntity on your entity resolver. What are the class names of the TransformerFactory and XMLFilter? Scenario 1 (Working): ___________ ___________ | | | | | |<----| App & | | Parser |---->| Handler | | | | | ----------- ----------- Scenario 2 (Not Working): ___________ ___________ ___________ | | x | | | | | |<----| |<----| App & | | Parser |---->| Filter |---->| Handler | | | | | x | | ----------- ----------- ----------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
