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=24826>. 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=24826 Transformer.transform is not thread safe (with nested xslt's) [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2003-11-19 17:06 ------- Ok. Will try to replace version shipped with WAS 5. As the last qustion: Javadoc says: "An Object of this class may not be used in multiple threads running concurrently. Different transformers may be used concurrently by different threads". Does it mean that Templates.newTransformer SHOULD return a fresh new instance of Transformer? If it so, does that instances reuse some common stuff? Because my problem is: Instance of Transformer is created for each thread(request) and discarded after request processing (as doc's say). But if there are 2 or more requests that will use the same cached Templates instance (to create new Transformer instace), both Transformers fails. In another words: there are different istances of Transformer, created by the same Templates instance and both fails - one with NullPointer, another produces incorrect result. More, this happens only if xslt, on which Templates is build, includes another xslt. If there are no <xsl:import/>/<xsl:include/> - all fine. PS. I can't change the status of this bug to "CLOSED", all I can do is to change resolution to "WONTFIX".
