Was the 'other side' (Berkely DB) in a separate process / machine? Or
part of the same jvm?
If separate, what clojure knowledge / libraries did the other side
have? I assume there was serialization across or else you wouldnt have
gotten the PersistentMap error.
And sounds like your passing the
On Sep 18, 8:51 am, noahr [EMAIL PROTECTED] wrote:
Was the 'other side' (Berkely DB) in a separate process / machine? Or
part of the same jvm?
Same JVM; I am running my Clojure application on the server and it
persists and retrieves data from Berkeley. It currently exposes an API
for a
Hello noahr,
I have created a library for myself to do persistence in Clojure to
Berkeley DB. I generally leverage Clojure's reader support for
(de)serialization.
However, in one instance I had to implement a particular interface and
pass that class as parameter to the Berkeley API.
At first
I've hit a problem trying to serialize an object from one (clojure)
server to another (java). I was *hoping* to simply use (PROXY) to
implement the object I want to send in clojure, and serialize that
across the stream. Unfortunately java barfs about:
java.io.NotSerializableException:
On Sep 12, 8:55 am, noahr [EMAIL PROTECTED] wrote:
So it looks like I will have to implement the object I want to send
across the stream in Java, not clojure (sigh)
Any ideas anyone?
If you've got Clojure available on both ends, you can serialize with
(pr-str...) and deserialize with
You wouldn't be able to execute any clojure created class or proxy
without having clojure available on the other side. You would have to
stream all of the dynamic classes that clojure creates (and each fn is
also a class), but also have available the clojure.lang stuff it
depends on to load and
