XOM API for Processing XML with Java

[Elliotte Harold <elharo AT metalab.unc.edu>]

I'm simply not willing to make any promises to anyone about XOM's thread 
safety, either for the current or future versions. I'm also not willing 
to promise that the underlying implementation will always be based on 
TrAX. Nor am am I willing to promise that it will be based on a TrAX 
Templates instead of a TrAX Transformer object. There's a reason none of 
this is specified in the public API or the API documentation. I'm trying 
to preserve my options for future development, and all of these things 
could change. It sounds to me like you're basing your design on 
knowledge of XOM's private parts, and that's dangerous.

In your use case, I would suggest using one XSLTransform per thread and, 
if that proves to be a performance sink, using a pool to hold a dozen or 
so reusable XSLTransform objects. I am not convinced there's a need to 
use the same XSLTransform object in several threads simultaneously, nor 
am I convinced that I can implement that in a safe fashion. The design 
here is very conservative. I'm trying to be careful not to promise more 
than I can deliver.

--
Elliotte Rusty Harold
elharo AT metalab.unc.edu