In JBM 2.0, each node will have its own high performance file based journalling persistent store, so will not require a relational database at all.
This should give much greater performance and scalability for persistent messages. So we won't need Hibernate for that.
There is an impedance mismatch between relational storage and messaging systems, you end up having to do nasty things to get them to work - they are fundamentally unsuited.
However, some people do like to see their messages in a database -for reporting purposes or whatever, so we will be creating a component that asynchonrously replicate messages from the journalling stores to a DB, this would be an optional component.
For this component we should definitely look at using Hibernate to abstract out the DB differences.
>>For this component we should definitely look at using Hibernate to abstract out the DB differences.
so, you guys have already started this ? shall i start cutting some hibernate code? Tim ?