DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=30885>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=30885 TransformerFactoryImpl.newXMLFilter bug with URIResolver Summary: TransformerFactoryImpl.newXMLFilter bug with URIResolver Product: XalanJ2 Version: 2.6 Platform: Other OS/Version: All Status: NEW Severity: Normal Priority: Other Component: org.apache.xalan.processor AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Inside TransformerFactoryImpl.newXMLFilter(Templates), there is line like this: --> return new TrAXFilter( templates ) Before the return, I believe this method should call TrAXFilter's m_transformer.setURIResolver (passing TransformerFactoryImpl.m_uriResolver), so that the "current" URIResolver is initialized for the filter. If it doesn't, there is *no way* to set the URIResolver used by the TrAXFilter. As a result, if the stylesheet upon which the TrAXFilter is based uses an XSLT "document" function, i.e. document('somescheme:some-scheme- part'), there is no way for the caller to handle these URIs. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
