My Account
The Java Data Objects (JDO) standard provides a unified, simple, and transparent persistence interface between Java application objects and data stores, and can significantly affect how deal with persistent data.

This category contains JDO related resources, including articles about JDO, JDO implementations and tools.
More information

Integrates Java objects, XML documents, SQL relational databases and LDAP directories in a unified model that allows information to be exchanged, persisted and manipulated in a variety of ways. Supports JDO. [Open Source, BSD-like]
A home page for JSR-000012, Java Data Objects.
The Proposed Final Draft of the JDO 1.1 specification for object-relational mapping on the Java platform.
Implementation of Sun's JDO specification (JSR 12), designed to support transparent persistence using any JDBC-compliant database. [Open source, Apache Software License]
Provides interface-based persistence to RDBMSs while allowing developers to focus on the object model, not the physical layer. It implements many of the interfaces specified by JDO. [Open source, GPL]
By Chris Richardson. Learn how to use Java Data Objects (JDO) to accelerate development and test domain model outside of the application server and without a database. (February 01, 2003)
This expert perspective lays it on the line: Exolab's Castor JDO product does not support the JDO standard. (December 04, 2002)
An in-depth look at using Castor's marshalling engine to do data binding of Java objects to tables, rows, and columns in an SQL database. (October 02, 2002)
In this scathing response to Don Bales' recent critique of Java Data Objects, David Jordan offers proof that JDO does not regard SQL as a bad thing, yields shorter and simpler code, and is vendor-neutral. (May 29, 2002)
Java Data Objects (JDO) is neither a silver bullet nor without merit. But its most important contribution may be to wake developers up to the coming paradigm shift: from database to objectbase, a place where not only data but data and behaviors are stored... (April 24, 2002)
The Proposed Final Draft of the JDO 1.1 specification for object-relational mapping on the Java platform.
A home page for JSR-000012, Java Data Objects.
Integrates Java objects, XML documents, SQL relational databases and LDAP directories in a unified model that allows information to be exchanged, persisted and manipulated in a variety of ways. Supports JDO. [Open Source, BSD-like]
Provides interface-based persistence to RDBMSs while allowing developers to focus on the object model, not the physical layer. It implements many of the interfaces specified by JDO. [Open source, GPL]
Implementation of Sun's JDO specification (JSR 12), designed to support transparent persistence using any JDBC-compliant database. [Open source, Apache Software License]
By Chris Richardson. Learn how to use Java Data Objects (JDO) to accelerate development and test domain model outside of the application server and without a database. (February 01, 2003)
This expert perspective lays it on the line: Exolab's Castor JDO product does not support the JDO standard. (December 04, 2002)
An in-depth look at using Castor's marshalling engine to do data binding of Java objects to tables, rows, and columns in an SQL database. (October 02, 2002)
In this scathing response to Don Bales' recent critique of Java Data Objects, David Jordan offers proof that JDO does not regard SQL as a bad thing, yields shorter and simpler code, and is vendor-neutral. (May 29, 2002)
Java Data Objects (JDO) is neither a silver bullet nor without merit. But its most important contribution may be to wake developers up to the coming paradigm shift: from database to objectbase, a place where not only data but data and behaviors are stored... (April 24, 2002)
Last update:
August 31, 2020 at 5:25:06 UTC
Computers
Games
Health
Home
News
Recreation
Reference
Regional
Science
Shopping
Society
Sports
All Languages
Arts
Business