You could always silo offending applications like that into their own containers - give them their own space and let them not affect the rest of your infrastructure. How you interact with that application/service may dictate your ability to do that cleanly, but those are larger architectural discussions.
Running multiple instances of Tomcat may or may not be in your interest, but it is certainly easy and well supported. -- Mike -----Original Message----- From: CBy [mailto:tom...@byrman.demon.nl] Sent: Wednesday, July 08, 2009 7:24 AM To: Tomcat Users List Subject: Problem with system property Hi, We have a third-party webapp that sets the following system property: System.setProperty("javax.xml.transform.TransformerFactory","net.sf.saxon.TransformerFactoryImpl"); This effectively forces all other webapps to use Saxon as an XLST/XQuery processor, see: http://java.sun.com/javase/6/docs/api/javax/xml/transform/TransformerFactory.html#newInstance%28%29 Other webapps, which are perfectly happy with the default, now suddenly have to include saxon9.jar to get successfully deployed. I can imagine conflicting webapps in the future. I feel a bit hijacked by this third-party application (we do not have the source code). What is the best way to deal with this? T.i.a. Carsten --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
