[jdom-interest] XSLTransformer.transform method - thread safe?

Clint.Redwood at xansa.com Clint.Redwood at xansa.com
Thu Nov 15 02:03:36 PST 2007


I've just had an XSL transform go VERY weird, and I think it may be that
two threads tried to use the same XSLTransformer object at the same time.
The result seemed to be that it returned the untransformed data.

I'm using the Saxon 8.9 XSLT2.0 Engine, and also there are some SAXON-SQL
queries in the XSLT in question.

The Javadoc states that the XSLTransformer is thread safe, but I'm not sure
if I've either found an issue with this, or if there's something not
threadsafe in the Saxon implementation.

Any suggestions as to how I could confirm this would be appreaciated as
I've not done much in the way of multi-threaded debugging.


Clint Redwood
Senior Solutions Architect - Boots Account
Xansa, a Steria company
t 0115 9595730 (Ext) 725730 (Int)
e clint.redwood at xansa.com
e clint.redwood at bcm-ltd.co.uk

Whilst this email has been checked for all known viruses, recipients should undertake their own virus checking as Xansa will not accept any liability whatsoever.

This email and any files transmitted with it are confidential and protected by client privilege.  It is solely for the use of the intended recipient.
Please delete it and notify the sender if you have received it in
error. Unauthorised use is prohibited.

Any opinions expressed in this email are those of the individual and not
necessarily the organisation.
     Xansa, Registered Office: 420 Thames Valley Park Drive,
     Thames Valley Park, Reading, RG6 1PU, UK.
     Registered in England No.1000954.
     t  +44 (0)8702 416181
     w  www.xansa.com

More information about the jdom-interest mailing list