IIRC Tomcat needs this stuff set only for validation: it doesn't
actually do _anything_ with the endorsed directories or their
contents to set up or influence any classloaders.
I think someone needs to do some experiments to determine:
- if the jars in endorsed need to be added explicitly to some
classloader
- if that classloader has to be the system (?? application??
boot??????) classloader or if any classloader that includes a jar in
endorsed gets to use the stuff in the jar in preference to the stuff
in the jvm.
My unvalidated impression agrees with Dain
thanks
david jencks
On Aug 25, 2006, at 7:44 PM, anita kulshreshtha wrote:
IIRC, The tomcat container needs to be started with
java.endorsed.dirs system property set to a dir where the xerces
parser
is available. It uses the endorsed dir mechanism to override the
default parser. The server manifest.mf contains an entry
Endorsed-Dirs: lib/endorsed
which is used by Deamon (read by CommandLineManifest) to set this
property before starting Geronimo. It should have been enough, but it
seems we have been adding it to the classpath also. I do not know if
this property is used by anyone else.
Thanks
Anita
--- Dain Sundstrom <[EMAIL PROTECTED]> wrote:
IIRC, they have to be on the classpath.
-dain
On Aug 25, 2006, at 12:21 PM, Jason Dillon wrote:
Anyone know if the jars in the endorsed dir need to be added to the
classpath... or will the jvm just suck up all *.jar files and load
them anyways?
Was just wondering that if that is the case, and we add them to the
classpath, does that just waste bytes for an unused classloader
and/
or slow down the initial boot?
--jason
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
