XOM API for Processing XML with Java

[Wolfgang Hoschek <whoschek AT lbl.gov>]

On Sep 10, 2004, at 6:44 PM, Elliotte Harold wrote:

> Nothing in XOM, including XSLTransform, is designed to be thread safe. 
> The assumption is you will not share objects between thread or, if you 
> do, you will take appropriate measures to synchronize.

I *know* that nothing in XOM is thread-safe, and I'm not asking you to 
put a single "synchronized" statement anywhere. This is not needed 
anyway. I'm asking for a XSLTransform design that does not *preclude* 
reasonable usage in multi-threaded environments.

If you'd think about what kind of synchronization measures it would 
take for a client framework to use XSLTransform in a general, yet 
reasonably efficient way you would probably understand.

The entire purpose of the TRAX Templates design is to allow sharing of 
compiled stylesheets in an implicitly thread-safe manner, and the 
implied performance gain is *dramatic* as you will know, in particular 
if using xalan XSLTC models. The current design defeats the entire idea 
of the TRAX Templates class.

Elliotte, take your time to actually read what I wrote in the last 
mails, and think about it for some time, will you, please :-)
Because I'm gonna give up now.