This is the mail archive of the
kawa@sources.redhat.com
mailing list for the Kawa project.
Re: why cant kawa.jar be put into Java/lib/ext/?
- From: Jim White <jim at pagesmiths dot com>
- To: "Hoehle, Joerg-Cyril" <Joerg-Cyril dot Hoehle at t-systems dot com>
- Cc: kawa at sources dot redhat dot com
- Date: Mon, 10 Nov 2003 12:15:41 -0800
- Subject: Re: why cant kawa.jar be put into Java/lib/ext/?
- References: <9F8582E37B2EE5498E76392AEDDCD3FE07DED8B6@G8PQD.blf01.telekom.de>
Hoehle, Joerg-Cyril wrote:
when I put kawa-1.7.jar into the Java JRE/lib/ext/ directory in order to
shorten command lines, suddenly -classpath seems to be ignored [*].
...
[*] actually, it's more complex than that. A system trace reveals that the
jars in the classpath are stat()'ed, but never open()'ed. Why?
That is a classloader security/sanity thing. I don't know all the
details, but the docs are here:
http://java.sun.com/j2se/1.3/docs/guide/extensions/index.html
If you want to put kawa.jar in lib/ext but not the other jars, you can
probably workaround the problem by using -Xbootclasspath.
Jim
--
"I love deadlines. I love the whooshing sound they make as they fly by."
-- Douglas Adams