IIRC you will get exceptions on a 1.4 JVM if xerces is not available
since the local attribute manager uses a few custom xerces properties.
-dain
On Aug 27, 2006, at 10:47 PM, Jason Dillon wrote:
I guess we could try omitting the xerces jars from the classpath of
server.jar and see if it works or not...
--jason
On Aug 26, 2006, at 5:41 PM, Heinz Drews wrote:
Everything loaded from directories specified by
-Djava.endorsed.dirs={dirlist} is loaded by the bootstrap
classloader.
The documentation in Tomcat indicates that the endorsed dirs are
managed differently. But the classes are visible in a classloader.
On 8/26/06, David Jencks <[EMAIL PROTECTED]> wrote:
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
