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=13116>. 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=13116 Custom URIResolver not called [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2003-10-03 15:51 ------- Phil, URIResolver's are used to resolve URIs in xsl:include, xsl:import, or document() function. [1] For your case, I think you want to be using EntityResolver [2] with a SAXSource or -ENTITYRESOLVER on the command line. And it also looks like there's no problem with incremental processing & a custom URIResolver in the latest CVS code. [1]http://xml.apache.org/xalan-j/apidocs/javax/xml/transform/URIResolver.html [2]http://xml.apache.org/xalan-j/apidocs/org/xml/sax/EntityResolver.html
