We're definitely going to need a generic RDB-backed persistence solution
at some point, so Derby would be a great place to start. It should only
take about two tables and a handful of vanilla SQL queries to replicate
what the bdb back-end is doing. Given this I suspect using an O/R layer
might be overkill and could prove to be slower than using JDBC directly.
--Rafael
Frank Lynch wrote:
I'd like to start working on a persistence solution for Qpid that will
be compatible with our apache licensed implementation. I've been
thinking about iBatis + Derby for this. I like the flexibility that
iBatis brings, as it allows users to tweak the database table
format/schema if necessary and its easy to slot in an enterprise
strength database (like Oracle, Sybase etc) in leiu of Derby.
Has anyone any opinions or thoughts on this, or should I just start
hacking away at an iBatis based persistence implementation?
cheers,
--Frank
