@Mark: I doubt that this will work. Unloading a namespace would mean
to remove a class from a classloader and this does not work in Java.
OSGi handles this by removing the bundle's classloader completely.
@All: The huge added value that OSGi still has is multi-version
support. Lets say I want to
There is rarely need to embed a runtime/framework into the OSGi
container itself. All that is needed is to refactor the Clojure
runtime to let OSGi do the class/resource loading. The goal would be
to get a central Clojure bundle and deploy application code into
separate bundles. For statically
Hi,
I am an OSGi enthusiast. Lately I have been looking at scheme and
clojure. I can't help but wonder if there are any genuine benefits
clojure can get from being a full OSGi citizen. It seems to me that
OSGi is to statically compiled Java what the REPL is for Clojure.
Except the REPL is more
It's possible to modify Clojure to run under OSGi (search the list
archives) but fundamentally they don't fit. OSGi assumes that it has
sole control of class loading. But Clojure needs its own
classloader. To make them cooperate, I think you would need to
integrate Clojure with the OSGi
There is this project going on:
http://wiki.github.com/romanroe/ogee
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from
I do have a novel idea to work around this but I've yet to put my theory to
code and publish it.
The problems I had when loading clojure based bundles into OSGi was that
after unloading, the classes remained loaded by the bundle providing RT.
The basic idea was to add a bundle listener to the
