To see how "standard" and "legal" this usage is, you can try enabling the security manager (the only way to control writing to system properties - which are always JVM wide, so since Tomcat uses JAXP, Tomcat cannot avoid being affected to some extent when a webapp changes the parser factory - is to use the security manager) :) The other problem is that this by defeinition won't behave the same in different VMs (1.4, and same if you have a 5.0 VM with the compatibility pack for TC 5.5).
Not allowing the application to modify this system property is not an option for me.
You can send me a WAR to test however, I would be interested to look at this alleged difference in behavior.
I've filled a bug report to which I attached a simple web app for reproducing the issue: http://issues.apache.org/bugzilla/show_bug.cgi?id=41759 Etienne --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
