Jackrabbit still has a very special place in my heart. I’ve fought it many times, sometimes losing, most of the time winning. But for over 7 years now, it is still the main storage engine serving the content of InfoQ. So this OrientDB engine for Jackrabbit by Thomas Kratz caught my attention:
This has some limitations, as jackrabbit will still access only one
node at a time, being able to traverse the graph at the storage
level is simply not intended by the whole api. But it works, it’s
readable, can be modified at the db level easily.
Original title and link: A Human-Readable Jackrabbit Persistence Manager Prototype for Orientdb ( ©myNoSQL)