Thanks Craig, but I think Im still not grokking it fully.
<snip>
Put your replacement parser into the "JDK Extensions" directory,
either $JAVA_HOME/jre/lib/ext or whatever directory you define on the
command line with the "java.endorsed.dirs" system property.
This is how Tomcat 4.1, 5.0, and the Java Web Services Developer
Pack 1.2 deal with this situation -- the parser they want to use
goes in the "$CATALINA_HOME/common/endorsed" directory
</snip>
Surely this means that the containers JVM would then be using the new parser
and thus every webapp running in that container would have to use it too -
or can each webapp have its own JVM with its own value for
java.endorsed.dirs?
You mention "non-JAXP-specified mechanisms" to select the parser. I presume
this means manually instantiating and calling the parsers specific
implementation class to parse the document? One would still have problems
though surely. For example if the jdk parser's version of
org.w3c.dom.whatever is different to the one in the 'local' parser which one
will get used? - and when its a different version of the same parser (with
the same named impl classes) then again your in trouble (like you mentioned
I would be if I used the discovery mechanism).
Im quite happy to do parser specific stuff (behind a suitable facade) of
course. (Id no more expect my app to run with a different parser version
(without testing and debugging) than I would expect to be able to just
anyhow ditch struts-1.1.jar and replace it with struts-1.0.2.jar!)
The issue of course if that if I try to sell a customer 'application X' that
only works properly with 'parser X' (because other parsers are full of bugs
or only support older apis), I dont want to have to tell her that she can no
longer run some other vendors 'application Y' that only works with 'parser
Y', nor do I wish to tell her to run a seperate container for each app as
neither of those choices is likely to impress her very much...
-----Original Message-----
From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 3 September 2003 13:48
To: Andrew Hill
Cc: Struts Users Mailing List
Subject: RE: [OT] XML Parsers vs WEB-INF/lib [WAS: RE: Commons Versions
bundled with Struts 1.1]
On Wed, 3 Sep 2003, Andrew Hill wrote:
> Date: Wed, 3 Sep 2003 11:58:13 +0800
> From: Andrew Hill <[EMAIL PROTECTED]>
> To: Craig R. McClanahan <[EMAIL PROTECTED]>
> Cc: Struts Users Mailing List <[EMAIL PROTECTED]>
> Subject: RE: [OT] XML Parsers vs WEB-INF/lib [WAS: RE: Commons Versions
> bundled with Struts 1.1]
>
> In other words, if Im running on a 1.4 JVM, _all_ the applications running
> in that container _must_ share the same parser? :-(
>
Not true, if you are willing to:
* Replace the "endorsed" parser as I described, or
* use non-JAXP-specified mechanisms to select your parser.
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
