JDOcentral.com will be a communication platform for the promotion and development of the JDO standard for transparent object persistence. It is intended to nurture grass roots support for the standard, encourage widespread adoption of the standard, and focus thought leadership for JDO products and services.
Much more than an informational vehicle, JDOcentral.com will be an interactive forum for activities such as organizing events, preparing an events calendar, distributing newsletters, and downloading JDO-related products. And despite essential sponsorship from commercial entities, the Web site will be focused on developing and promoting the JDO standard for the benefit of all.

Nowadays the combination of Java DataBase Connectivity (JDBC) and relational databases is very popular for the development of database applications in the Java Standard Edition. Nevertheless it is clear that the object-oriented paradigm behind Java doesn't agree with the relational model. Developers need to design both the database and the code, and manually map the objects to the database values. This document contains the evaluation of Java Data Objects (JDO), a technology that allows to persist objects to the database. It bridges the gap between the Java object model and the SQL relational model by providing a very natural object-oriented interface to store and retrieve Java objects. With JDO, developers can work on the business solution, without worrying about the code to map between objects and databases. We'll trace the advantages and disadvantages of JDO against the current JDBC (v3.0) technology during the software development cycle of a new product. My hypothesis states that JDO has several advantages against the JDBC method during the evolution of a Java databank application. I also state that JDO decreases the performance penalty.