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 t
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/
On 3/3/07, Etienne Giraudy <[EMAIL PROTECTED]> wrote:
Shall this be considered as a regression as in that case tomcat
configuration is somehow altered by a web app?
(in that case I'll fill a bug in bugzilla))
I don't think there can be a change of behavior in this sort of thing
between TC 5.5 a
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 th
> 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.
