tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From CBy <>
Subject Problem with system property
Date Wed, 08 Jul 2009 11:23:34 GMT

We have a third-party webapp that sets the following system property:


This effectively forces all other webapps to use Saxon as an XLST/XQuery 
processor, see:

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?



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message