|
The JDO Object Model
The JAVA DATA Objects (JDO) API is being
defined within Sun’s Java Community
Process. It is establishing a standard for
transparent persistence of Java objects in
transactional datastores. Commercial implementa-tions
enhancements are required
for the class to support
transparent persistence in
a JDO runtime environ-ment.
|
|
Using Java Data Objects
In this article, I'll discuss Sun's Java Data Objects (JDO) standard. JDO allows you to persist Java objects, supporting transactions and multiple users. It differs from JDBC in that you don't have to think about SQL and "all that database stuff." It differs from serialization as it allows multiple users and transactions. This standard allows Java developers to use their object model as a data model, too. There is no need to spend time going between the "data" side and the "object" side.
|
|
"Castor JDO": Simply False Advertising
The Exolab Group is an informal organization that develops open source enterprise software. I ran across Exolab a few years ago while looking for a facility to provide a mapping between Java object models and XML data. I wanted to store the Java objects using an implementation of the Object Data Management Group (ODMG) standard.
|
|
Using Castor JDO for SQL Mapping
Castor is a multifaceted software tool being developed under the auspices of exolab.org, an informal organization involved in the development of open source, enterprise software projects based on Java and XML.
|
|
Flawed Understanding of JDO Leads to FUD
When a new technology comes along that introduces a paradigm shift, it often challenges the existing, established technology in use. It is a natural tendency for those with a vested interest in maintaining the status quo to spread fear, uncertainty, and doubt (FUD) about the new technology. Java Data Objects (JDO) is a new technology released from the Java Community Process that allows developers to directly persist their object models in transactional datastores.
|
|
JDO vs. Entity Beans: A Modest Proposal
When Sun introduced the EJB 1.1 spec (including Entity Beans) two years ago, it was a revolution in enterprise computing. Experience revealed, however, that it was not perfect. The remote interface is slow and it makes creation of fine-grained objects difficult, in many cases.
|
|
The Debate Over Java Data Objects
Java programmers like working with objects (I hope!). Applications often, if not always, need us to persist information. Most server-side developers have worked with the JDBC API, which allows us to access databases, and is mainly used to query relational databases. Since we already have our model in our objects, wouldn't it be nice to be able to persist the objects that it makes sense to store?
|
|
Coming Out of the JDO Closet
As part of building the infrastructures for a large J2EE project, we've spent the last few months designing and implementing a JDO-based O/R persistency framework. This framework provides our business logic programmers with the following features: an interface-based abstract view of the data-layer with full OO semantics, zero-need knowledge of the object-to-database mapping details, "delta" support, and more. This article presents the persistency framework that we've built on top of JDO, and offers a commentary on the current advantages and shortcomings based on our experience with the JDO specification.
|
|
Close-up on JDO: a standard for persistence of Java business objects
In July 2000, Sun came up with a new data access technology which could have a major impact on the way Java applications are created. Standardized under the name JDO (Java Data Objects), this technology will enable real business object modeling to be carried out by automatically managing interaction between objects and resource managers. Traditional development using a specific, non-object access API such as JDBC will now, with JDO, have a standardized alternative
|
|
JDO: An initial Tour
Java is a language that defines a runtime environment in which user-defined classes
execute.Instances of these user-defined classes may represent real-world data that is
stored in a database,filesystem,or mainframe transaction processing system.Addi-
tionally,small-footprint environments often require a means of managing persistent
data in local storage.
|
|
Using and Understanding JDO
THE JDO LEARNING TOOLS are a small but comprehensive set of programs that you
can use for several purposes. You can use them as an introduction to JDO. You can use
them to verify what you have learned about JDO.
|
|
The JDO Query Language
|
|
A Comparison Between Java Data Objects (JDO), Serialization and JDBC for Java Persistence
SQLJ enables applications programmers to embed SQL operations in Java code in a way that is compatible with the Java design philosophy. A SQLJ program is a Java program containing embedded SQL statements that comply with the ISO-standard SQLJ Language Reference syntax. Oracle9i SQLJ supports the SQLJ ISO standard specification.
|
|
Java Data Objects - The Future for Java Object Persistence
|
|
Why JDO is a Critical Component of J2EE?
|
|
OpenFusion - Java Data Objects
|
|
JDO or CMP?
JDO's design center is making Plain Old Java Objects (POJOs) persistent in any tier of an enterprise architecture, while CMP's solution is container-bound with elaborate requirements for development and deployment.
|
|
Flawed JDO Points the Way to the "Objectbase"
There's been a lot of hype lately about Java Data Objects (JDO). It appears to be the new silver bullet that will alleviate all of our coding drudgery. JDO threatens the livelihood of products such as object/relational mapping utilities that map Java objects to relational data. Because of this, and for other reasons, JDO has received more than its fair share of bad press. To be fair however, JDO does have it merits.
|
|
Using OJB as a persistence layer in your applications
This document demonstrates how to use the ObJectRelationalBridge (OJB) object/relational mapping in a simple application scenario. The tutorial application implements a product catalog database with some basic use cases. The source code for the tutorial application is shipped with the OJB source distribution and resides in the package
|