While working on the content repository, we felt it was easy to store data, but sometimes awkward to organize it in a way that was easy and friendly to work with java objects.
So we've developed something called a bean coder for our application. We've made it open source in case other people would want to use it. With it, you can easily persist some java beans to the repository, and retrieve them at any time.
The cool thing is that it plays nicely with the available repository searches facility so that you can quickly and easily retrieve any of the persisted objects, list or maps of beans.
A short how-to is available at the following URL:
Not sure this is suitable for everyone, especially people concerned with more complete solutions, but this has been in production and working very well so far in our environment (50 servers), so just felt like we should
contribute back something to the java community.
It's already integrated and used in different strategic places in the magnolia CMS (http://www.magnolia.info) for persisting/loading configuration of the server and also for building inbox from active workflow items.
It can of course be used with any compatible JCR repository such as jackrabbit. (http://jackrabbit.apache.org/)
As said above, it just works, and has already been in production for some time. What would be nice now is to get scenario such as:
- how to extend the library
- how would other use it
- if this is actually used, would it make sense to spawn a completely separate projects for it ?
Comments ? Ideas ?
Log in to post a comment.