JRuby and DB4O: More Info

Upon investigation, I found that JRuby throws a wrapper around Java objects in some circumstances. The wrapped object cannot be saved by DB4O, or so I have concluded. My follow up strategy was going to be to define a class in java and try to instantiate it in JRuby to see if it would save to a file. I may be on the right track.

A search of the Db4O forums has led me to the following excellent information, provided by Jason Thomas. I will attempt to make use of this information, and I will write about the result. While you wait, follow the link I have posted above – it is interesting.

Note: (Added November 20, 2008) I have since returned to my investigations of how to use DB4O using scripting languages running on the JVM. See my work with Jython and the Django framework using DB4O. My BS theory of JRuby throwing a wrapper around Java objects is probably out to lunch. I may come back to this, but feel free to see what I am doing with Jython to see if it applies to JRuby.