On 3/4/07, Etienne Giraudy <[EMAIL PROTECTED]> wrote:
I guess that the point that is questionnable here is the way the API
is designed: modifying the system property 'legal' and, AFAIK, it is
the only way to choose the parser implementation we want to use
(http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/parsers/SAXParser.html).
From that point of view, shouldn't Tomcat protect itself against
bad-designed standard APIs usage?
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).
You can send me a WAR to test however, I would be interested to look
at this alleged difference in behavior.
Rémy
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
