I found the answer and fixed it and it works!
Yes, *use-context-classloader* is true by default.
But, the context classloader wasn't the right classloader, so I had to
set context classloader to the right classloader, at the right place
before any clojure code is called like this:
Clojure does use the context classloader by default for its root
classloader (on top of which it sometimes creates new
DynamicCLassloaders). This behaviour is controlled by the value of
*use-context-classloader*, which is true by default.
I don't have any java web start experience, so I'm
Also I should note that all my clojure code is compiled to classes and
the classes are jarred and sent to the Java Web Start program along
with clojure.jar.
On Jul 4, 3:53 am, Nick Mudge mud...@gmail.com wrote:
I am writing a 3rd party module in Clojure for a Java Web Start
application written
Is there a way to tell which classloader clojure is using?
On Jul 5, 4:53 am, Chas Emerick cemer...@snowtide.com wrote:
Clojure does use the context classloader by default for its root
classloader (on top of which it sometimes creates new
DynamicCLassloaders). This behaviour is
I am writing a 3rd party module in Clojure for a Java Web Start
application written in Java.
I am using Clojure 1.1.
I think that my clojure program and clojure.jar are on the classpath
and are being loaded because when clojure.jar is not seen on the class
path this error results:
