Java201.com

• JCredo   - [Clicks: 133]
  Its free 100% compliant JDO implementation, together with JBuilder integration, full JDO open source code example and support services. This new version of JCredo already includes some JDO 2.0 spec. features such as named queries and advanced features like built-in L2 cache, prepared statements caching and batch execution, full support of Java collection framework, native SQL support in queries, query extensions and transaction flushing.
  http://www.jcredo.com/home/index.jsp
• JPOX Java Persistent Objects JDO   - [Clicks: 214]
  With a versatile and high performance implementation, JPOX is on the cutting edge of the available Java Data Objects (JDO) implementations, offering a free and full compliant JDO implementation released under an open source license. JPOX 1.0 is fully compliant with JDO 1.01, and JPOX 1.1 has many JDO 2.0 preview features. If you are interested in using a JDO implementation and make the most of your time, download JPOX and see what you think. This website provides various documents defining the current status of JPOX with regards functionality and how well it meets the JDO specification. Our future roadmap is available on this site, as well.
  http://www.jpox.org/index.jsp
• TriActive JDO (TJDO)   - [Clicks: 57]
  TriActive JDO (TJDO) is an open source implementation of Sun's JDO specification (JSR 12), designed to support transparent persistence using any JDBC-compliant database. Although the project is formally in beta release, TJDO is currently deployed and running successfully in a number of commercial installations.
  http://tjdo.sourceforge.net/
• XORM   - [Clicks: 62]
  XORM is an extensible object-relational mapping layer for Java applications. It provides interface-based persistence to RDBMSs while allowing developers to focus on the object model, not the physical layer. XORM uses the API described by the Java Data Objects (JDO) specification (JSR 12) and implements many of the interfaces specified by JDO. In contrast to most JDO implementations, XORM does not require you to run a class-file enhancer before deploying your persistence-capable classes. Instead, XORM allows you to specify persistence-capable classes using abstract classes or interfaces; bean-style get()/set() methods are enhanced at runtime to be managed for persistence.
  http://xorm.sourceforge.net/

[Top]