Thanks, I'll try the direct instantiation. I've already renounced
portability by extensive use of the Saxon flavor of Common Java Binding in
order to implement Java ResourceBundle and MessageFormat methods in xsl.
[mailto:saxon-help-admin@... Behalf Of Michael Kay
Sent: Tuesday, November 18, 2003 12:26 PM
Subject: RE: [saxon] Websphere 4
> Yes, I have done that. I put this line of code in the init()
> method of a servlet that is loaded at start-up:
> This seems to cause Websphere to use Saxon for all its XML
> transforming, and it works fine when my web app starts up
> along with Websphere. If Websphere has already used XML
> transforms before my web app starts, though, it leads to some
> confusion. (Presumably this would cause other web apps in the
> same server to use Saxon for their XML transforming as well.)
To add some ideas (there may be drawbacks):
If you don't want to run the risk of other apps picking up the system
property, you can always try instantiating the Saxon TransformerFactory
TransformerFactory f = TransformerFactory.newInstance();
TransformerFactory f = new com.icl.saxon.TransformerFactory();
or if you don't want a compile-time reference to the class, you could
instantiate it dynamically using newInstance().
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
saxon-help mailing list
The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.