On 3/3/07, Caldarale, Charles R <[EMAIL PROTECTED]> wrote:
> From: Etienne Giraudy [mailto:[EMAIL PROTECTED]
> Subject: Migration from 5.5.20 to 6.0.10: parser issue on
> application deployment
>
> One of the web app running on that server includes
> xercesImpl.jar and use it through modifying the system
> property javax.xml.parsers.SAXParserFactory.
That behavior looks rather questionable to me. Having a webapp modify a
global property that has the potential of affecting everything running
in that JVM - including other webapps and the container - seems like a
very risky strategy, raising serious compatibility and operability
issues. The fact that it happened to work in one version of one
container doesn't imply that it's an appropriate thing to do.
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?
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]
