Scripting Languages And DB4O

I have developed an interest in getting DB4O to work with scripting languages, as regular readers of this blog will know. I have had less time this week than I would like, but I will be posting some examples of DB4O working with Jython.

 I have been thinking of building a small web-enabled repository using Jetty or Restlets with Jython and DB4O. Sorry if this does not happen instantly, but it will happen.

I also want to return to Ruby on Rails running on JRuby – I would like to look at integrating DB4O support with Active Resources. It would be nice to define a model and get DB4O CRUD at no additional cost – this seems like a worthwile effort, and it would be good to get experience with Active Resource.

Then, after tackling RoR and Jython, I would like to try my hand at using DB4O from Quercus. Quercus is an implementation of PHP that runs on the JVM, giving PHP the ability to use Java libraries like DB4O.

Later, I would also like to try to use DB4O from Grails, another Ruby on Rails derivative that runs on the JVM using Groovy. The possibilities for DB4O are huge – DB4O can go wherever the JVM can go.

It looks like Microsoft’s common language runtime approach is taking the Java world by storm – the JVM is becoming the new CLR. For a long while now, it has been possible to author applications in multiple languages and run them under .NET or Mono. I think that is a good idea. Java is on the right track – it has to become easier to write applications that run on the JVM.

Obviously, DB4O is available in any language that runs on the CLR. However, I just want to make note of the trend of running scripting languages on the JVM – this opens the doors for DB4O in many important ways.

When I has some solid code, and a tutorial to go with it, I will begin posting in the DB4O forums.