Sweet. Thanks!
On Tue, Aug 20, 2013 at 3:51 PM, Toby Crawley t...@tcrawley.org wrote:
David Pollak writes:
I have an application where I need multiple independent Clojure contexts
running in the same JVM.
You can use ShimDandy[1] to load multiple Clojure runtimes in the same
JVM, and
be cast to
clojure.lang.IFn
It seems that someplace the clojure.lang.IFn interface is being loaded
around my classloader.
Can someone point me to a way to run multiple Clojure contexts in the same
JVM?
Thanks,
David
PS -- Interestingly, invoking RT.loadResourceScript via reflection works
just
reflection), I wind up with:
java.lang.ClassCastException: clojure.core$eval1 cannot be cast to
clojure.lang.IFn
It seems that someplace the clojure.lang.IFn interface is being loaded
around my classloader.
Can someone point me to a way to run multiple Clojure contexts in the same
JVM?
Thanks
point me to a way to run multiple Clojure contexts in the
same
JVM?
Thanks,
David
PS -- Interestingly, invoking RT.loadResourceScript via reflection works
just fine... so my current workaround is to do that... but it's less than
optimal.
--
Telegram, Simply Beautiful CMS
David Pollak feeder.of.the.be...@gmail.com writes:
I have an application where I need multiple independent Clojure contexts
running in the same JVM.
Classlojure [1] can do this for you, taking care of correct
initialisation, and evaluation.
[1] https://github.com/flatland/classlojure
David Pollak writes:
I have an application where I need multiple independent Clojure contexts
running in the same JVM.
You can use ShimDandy[1] to load multiple Clojure runtimes in the same
JVM, and call into those runtimes from Java. That's what Immutant[2] and
the Clojure language module