Apache Object/Relational Bridge (OJB) is an Object/Relational mapping tool that allows transparent persistence for Java objects against relational databases.

The OJB team recently announced the 1.0.4 release, with copious notes as follows:

New Features:
* Support for embedded & network Derby (only distinct count queries don't  work yet)
* Added ability to prepare the database for OJB's unit tests via DdlUtils  (instead of Torque)
Note that this is required when running the tests against Derby
* [OJB-10] - Configurable Proxy generation (including CGLIB based generation)
* [OJB-31] - Configurable JDBC driver-setting setFetchSize
* [OJB-14] - Setting custom JDBC driver tuning options trough jdbc-connection-descriptor
* [OJB-6] - Support for stored procedures returning ResultSet.
* [OJB-41] - ODMG-api: Allow cascading delete using auto-delete setting in metadata
* [OJB-66] - Allow to specify a sequence start element for SequenceManagerNextValImpl. Fixed for Oracle, PostgreSQL, MaxDB/SapDB, DB2. Additionally sequence properties like 'increment by', 'cache', 'order',... are supported too. See 'sequence manger' guide and javadoc
* Add new ODMG extensions and configuration properties. All properties can be set
at runtime as global property in class ImplementationExt and for a specific transaction in class TransactionExt:
- 'ordering' Allow to dis-/enable OJB's object ordering on transaction commit
- 'implicitLocking' Dis-/enable OJB's implicit locking
* Add new property 'TxCheck' in OJB.properties file. When enabled, on PB store anddelete calls OJB checks for a running PB-tx, if not found an error is logged in order to avoid store/delete calls without a running PB-tx (while development).