Hi there,
I have been doing a little digging around as a result of trying to build the
Ozone CVS on my machine and made a discovery. Ozone is not really an Object
Database, I believe. Let me explain...
Ozone is an XML database. Ozone uses a framework called Castor to implement
a mapping from Java Object into XML. Castor is also an O/R mapping tool and
is, apparently, going to be used in OpenEJB as it's O/R tool.
All of this set me thinking that integrating Ozone might not be a good idea
as you're not gaining anything - you're still using a mapping tool and not
storing to a 'true' object database.
If anyone knows better than me about this, or has any thought or opinions,
I'd appreciate them sharing them with the group.
Regards,
Peter.