|Deletions are marked like this.||Additions are marked like this.|
|Line 85:||Line 85:|
|Apache JDO 2.0 beta is now available. See the [http://db.apache.org/jdo/index.html Apache JDO web site] for more information.||Apache JDO 2.1 is currently being tested for release.|
|Line 87:||Line 87:|
|The release testing plan is described at ReleaseTesting.||The release testing results are at ReleaseTesting2dot1.|
1. About JDO
Java Data Objects (JDO) is a standard way to access persistent data in databases, using plain old Java objects (POJO) to represent persistent data. The approach separates data manipulation (done by accessing Java data members in the Java domain objects) from database manipulation (done by calling the JDO interface methods). This separation of concerns leads to a high degree of independence of the Java view of data from the database view of the data.
Interfaces are defined for the user's view of persistence:
PersistenceManager: the component responsible for the life cycle of persistent instances, Query factory, and Transaction access
- Query: the component responsible for querying the datastore and returning persistent instances or values
- Transaction: the component responsible for initiating and completing transactions
Commercial and open source implementations of JDO are available for relational databases, object databases, and file systems.
JDO is being developed as a Java Specification Request in the Java Community Process. The original JDO 1.0 is JSR-12 http://www.jcp.org/en/jsr/detail?id=12 and the current JDO 2.0 is JSR-243 http://www.jcp.org/en/jsr/detail?id=243. JSR-243 has been approved by the Executive Committee of the JCP http://jcp.org/en/jsr/results?id=3663
JSR-243 is now in maintenance. For a list of issues to be resolved in maintenance, please see the ChangeLog.
2. Current Development Activities
3. Design Work
Designing a ScalableBackEnd for an implementation of Apache JDO similar to FOStore but scalable using a queryable back end.
4. About Apache JDO
Sun Microsystems has decided to donate Java Data Objects (JDO) to the open source community. Both of the specifications will be developed in the Apache JDO project. We envision several sub-projects to be developed as part of this project:
- JDO 1.0 API. This is the standard definition of the JDO API as defined by the published JSR-12 standard.
- JDO 1.1 Reference Implementation. This is a file-based, single-user store for persistent Java objects. The version number is 1.1 to reflect that the Java package has changed from com.sun.jdori to org.apache.jdo. The license terms have also changed.
JDO 1.1 Technology Compatibility Kit. This set of programs tests that a JDO 1.0 implementation is in compliance with the standard. The version number is 1.1 to reflect that the test framework has changed from [http://java.sun.com/developer/technicalArticles/JCPtools2/ JavaTest] (a proprietary Sun package not suitable for open source projects) to[http://www.junit.org/index.htm JUnit], an open source test framework. The license terms have also changed.
- JDO 2.0 API. This is the standard definition of the JDO API as defined by the JSR-243 standard currently under development.
- JDO 2.0 Technology Compatibility Kit. This set of programs tests that a JDO 2.0 implementation is in compliance with the standard.
JDO 2.0 FOStore (File Object Store) implementation. This is an implementation of JDO 2.0 based on the JDO 1.0 Reference Implementation. It does not support relational data access, so it is inappropriate for the JDO 2.0 Reference Implementation. We are investigating [http://sleepycat.com SleepyCat] for the back end. See SleepyCatIntegration for discussion of the JDO/SleepyCat integration.
- JDO 2.0 Geronimo Integration. This project will build the glue between the JDO 2.0 Reference Implementation and the J2EE compliant application server. We expect to use a common persistence framework (Tranql) to provide both EJB3 and JDO persistence services.
Due to timing constraints, the JDO 2.0 Reference Implementation is not being built as an Apache project, but will be built as a JPOX release http://jpox.org.
5. Project Structure
For more information on the structure of the project, see ProjectStructure.
This project will use:
WiKi for general project communications;
[http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10630 ASF JIRA] for issue tracking;
[http://subversion.tigris.org/ subversion] for source control;
[http://maven.apache.org/ maven] for build;
- test first philosophy.
If you are interested in participating in the JDO project, please subscribe to a [http://db.apache.org/jdo/mail-lists.html mailing list] to find out what's happening.
If you're interested in committing to the project:
You'll need to fill out some legal paperwork and go through a process to get an apache committer account: See [http://apache.org/dev/new-committers-guide.html New Committers Guide], [http://apache.org/dev/contributors.html Contributors], and [http://apache.org/dev/committers.html Committers] for more details.
After you've received an email from email@example.com with your committer account information, change your initial password: Login by 'ssh -l <username> cvs.apache.org' (soon 'people.apache.org', as by apache email announcement); run 'passwd'; run 'svnpasswd'. See [http://apache.org/dev/version-control.html Committer Subversion Access].
Check out the JDO sources and test your [http://db.apache.org/jdo/svn.html subversion] account.
Sign up for an [http://issues.apache.org/jira/ ASF JIRA] account.
We have a communications conference call every Friday at 9:00 AM Pacific time. The conference call number is 866 230-6968 (international 865 544-7856) code 294-0479#. During this call we discuss project status, issues, concerns, and strategy. Everyone interested in Apache JDO is welcome and encouraged to participate.
8. Technology Compatibility Kit Developer's Page
Information for developers of the JDO TCK is found at TechnologyCompatibilityKit21
The list of TCK20 challenges is found at ["TCKChallenges"]
Apache JDO 2.1 is currently being tested for release.
The release testing results are at ReleaseTesting2dot1.
The release manager must have a key to sign the release. Learn about key signing and creating a key at KeySigning.
10. General Developer Information
JDO uses the same [http://wiki.apache.org/geronimo/CodingStandards coding standards] as the Geronimo project.
There are a number of items on the ToDoList. You can volunteer for any of them...
The subversion repository has been set up. You can take a look at http://db.apache.org/jdo/svn.html for more information.
The apache JDO project uses maven for build. You can take a look at the MavenInfo page for more information.
The JDO sub-projects ri11 and tck11 make use of the apache commons logging package. You can take a look at the LoggingDetails page for more information.
- The objective of JDO is to support J2SE 1.3 for runtime. You find details about running with J2SE 1.3 at the ["J2SESupport"] page.
A DeveloperScratchpad is available for uncategorized issues.
11. JDO Resources
[http://java.sun.com/products/jdo Sun's official JDO site]
[http://db.apache.org/jdo/index.html Apache JDO site]
[http://www.java201.com/resources/browse/61-all.html JDO-related resources] - Articles, Books, Presentations, Tutorials.
12. 'Special' Wiki pages
- A list of all pages on this wiki.
A basic guide to the MoinMoin wiki (including information about wiki syntax).
- A list of all the words that appear in the titles of the pages on this wiki, with links to pages that include that word.
- A full-text search of the wiki.
- All the "broken links" -- a list of all the pages on this wiki that are linked to, but do not exist.
- All pages on this wiki that are not linked to from anywhere else (and are thus very hard to reach).
- Generates a list of 75 random pages on this wiki.
- Generates a graph and some statistics about the sizes of pages on this wiki.
- Generates a graph of page views and page visits.
- Generates a graph of the web browsers used in visiting this page.
- Shows basic information about this wiki installation, the extensions it has installed, etc.