You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by bu...@apache.org on 2002/10/28 18:10:03 UTC

DO NOT REPLY [Bug 11648] - Transformer doesn't keep URIResolver from Templates

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

Transformer doesn't keep URIResolver from Templates

mkwan@ca.ibm.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From mkwan@ca.ibm.com  2002-10-28 17:10 -------
Both TransformerFactory and Transformer have a setURIResolver() interface, 
which means that you can use different URI resolvers for them. It is not 
required by JAXP that TransformerFactory should pass the URI resolver to the 
Transformer. As a safe bet, you should always call Transformer.setURIResolver() 
if you want to use a customized URI resolver for the transformation.

I admit that it would be better if the two usages (Transformer and Templates) 
have the same behavior. If it is a minor change, I would like to put it in. 
However, the change seems to big and I don't want to change a lot of code for a 
minor enhancement.