This is the mail archive of the
kawa@sources.redhat.com
mailing list for the Kawa project.
why cant kawa.jar be put into Java/lib/ext/?
- From: "Hoehle, Joerg-Cyril" <Joerg-Cyril dot Hoehle at t-systems dot com>
- To: kawa at sources dot redhat dot com
- Date: Mon, 10 Nov 2003 15:22:53 +0100
- Subject: why cant kawa.jar be put into Java/lib/ext/?
Hi,
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 [*].
Example 1:
java -cp xercesImpl.jar:xml-apis.jar kawa.repl
#|kawa:1|# (invoke-static <org.apache.xerces.impl.dv.util.Base64> 'decode "ABCD")
java.lang.RuntimeException: no such class: org.apache.xerces.impl.dv.util.Base64
at gnu.bytecode.ObjectType.getReflectClass(ObjectType.java:74)
Example2:
Similarly when I put it into JDK/JRE/lib/ext (Tomcat uses JDK, not JRE, for unknown reasons), I got
messages like cannot find javax.servlet.http.HttpServlet when trying to invoke a BRL URL
(while tomcat, servlets and jsp continued to work fine).
Removing the jar from Java's central directory solved the problem.
How can this be explained?
How to get rid of this bad behaviour?
May this be related to the fact that kawa can be used via java -jar kawa.jar
(i.e. runnable jar file)??
[*] 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?
Regards,
Jorg Hohle