} 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
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
.
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
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
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
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
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
On 8/25/06, Jason Dillon [EMAIL PROTECTED] 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?
No, they needn't.
An excerpt from 'Endorsed Standards Classes Deployment'
But, do they automatically make it onto the classpath? This snip
does not really lead me to believe that it does or does not.
--jason
On Aug 25, 2006, at 12:43 PM, Jacek Laskowski wrote:
On 8/25/06, Jason Dillon [EMAIL PROTECTED] wrote:
Anyone know if the jars in the endorsed dir need to
On 8/25/06, Jason Dillon [EMAIL PROTECTED] wrote:
But, do they automatically make it onto the classpath? This snip
does not really lead me to believe that it does or does not.
Well, I wish I could test it out, but don't know how. I have never
used it explicitly. I'm pretty sure it doesn't
It is my recollection that we assumed they were automatically added
and the reality was they weren't so I had to add them explicitly to
the manifest class path.
-dain
On Aug 25, 2006, at 12:54 PM, Jacek Laskowski wrote:
On 8/25/06, Jason Dillon [EMAIL PROTECTED] wrote:
But, do they
Okay.
--jason
On Aug 25, 2006, at 1:11 PM, Dain Sundstrom wrote:
It is my recollection that we assumed they were automatically added
and the reality was they weren't so I had to add them explicitly to
the manifest class path.
-dain
On Aug 25, 2006, at 12:54 PM, Jacek Laskowski 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
13 matches
Mail list logo
