Jeanfrancois Arcand wrote:
[back from vacation :-)]
Costin Manolache wrote:
Shapira, Yoav wrote:
Hi, I have a couple of only-slightly-related comments, but related nonetheless so I'll put them here.
Re: endorsed directories. Do we still want to support JDK 1.3 in Tomcat
5.1? Since we're gearing up for JDK 1.5, we might want to make 1.4 the
minimum. I'm +0.5 on this.
First, endorsed directories are _not_ for 1.3, but for 1.4 ( to override the build-in parser and the check they do on load ).
1.3 works fine with just having the parser in classpath, or in /jre/lib/ext, and it's quite simple to add code to the loader to add the parser packages only if 1.3 is detected.
Except if you turn validation on, which will not works since XML schema is not supported in Crimson or early version of Xerces (remember the nightmare....)
I'm using JDK1.3 most of the time, and I think a lot of other people and companies are still using it. I don't mind having the default distribution built for 1.4+ ( no xerces ), with instructions on how to get the additional jars for 1.3. But I think it would be very bad to not be able to run in 1.3 - and I don't see any good reason to justify forcing the users to upgrade.
One question we should explore is do we really wants to have a dependencies on Xerces? Like you already said, a pull parser might be better, smaller and more stable than having to rely on Xerces. Not sure if pull parser supports schema yet...
+1 of dropping Xerces ;-)
Couldn't the use of XML be forced in a manner that is completely independent of JAXP? This could try for the 1.5 Xerces (once at startup) and then fail over to the 1.4 Xerces which it would always deliver, etc.
Just a thought....
-- Jess Holle
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
