[ http://issues.apache.org/jira/browse/XALANJ-1930?page=all ]
Brian Minchau updated XALANJ-1930:
----------------------------------
Version: Latest Development Code
(was: 2.6)
> TransformerFactoryImpl.newXMLFilter bug with URIResolver
> --------------------------------------------------------
>
> Key: XALANJ-1930
> URL: http://issues.apache.org/jira/browse/XALANJ-1930
> Project: XalanJ2
> Type: Bug
> Components: transformation, Xalan-interpretive
> Versions: Latest Development Code
> Environment: Operating System: All
> Platform: Other
> Reporter: Greg
> Assignee: Xalan Developers Mailing List
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
