Xcalia has released LiDO XD 3.1, a transparent object persistence engine that can map objects to RBMS', XML files, the filesystem and several mainframes. LiDO XD 3.1 includes performance and scalability improvements, full JMX admin, and many new JDO 2.0 preview features. XD will eventually support EJB 3 POJO's as well as SDO.
JDO 2.0 preview features:
• FetchPlan and named fetch groups,
• JDOQL 2.0 projections and aggregates,
• JDOQL 2.0 String.matches(String) support
• PersistenceManager's flush() and checkConsistency() APIs,
• DataStoreCache interface,
• JDOConnection interface,
• User-defined persistence interfaces,
• Deletion by query,
Additionally, there are many noteworthy LiDO-specific features:
• Transparent logical deletion, whereby deleted objects are only marked as deleted in the database, are not actually deleted, and do not appear in subsequent queries or object references,
• Symbolic collections, where only those elements in a collection that must be loaded actually are,
• Performance profiles, where a user can easily specify a profile name, causing appropriate changes to made to relevant performance settings,
• User-defined field filtering,
• Synthetic fields, where data can be tracked with an object without that object having to maintain a field for it,
• Improved JCA integration,
• Second-level caching policy improvements, including timeout-based and scheduled,
• Configurable number of retries upon certain exceptions during commit,
• Reverse foreign-key unary relationships,
• Several documentation improvements, including a new object-relational mapping quick reference guide,
and many others.
Lido 3.1 also comes with a new free license that allows developers to use the product 30 minutes at a time for as long as they need.
Check out Lido XD 3.1 announcement