Sun Endorses ODMG Database Storage Specification for Java
Articles and Tips: article
01 Sep 1997
Sun Microsystems, Inc. recently announced that it has endorsed the ODMG Binding for Java, a database storage API specification written for Java and published by the Object Database Management Group, an independent standards body.
The ODMG Binding for Java specification will enable developers to simply and easily build cross-platform Java applications that automatically store Java objects in databases. The complex programming task of connecting applications to a wide variety of databases is greatly simplified with ODMG's API.
"Developers need a standard way to build Java applications that store objects in databases," said Rick Cattell, chair of the Object Database Management Group and a distinguished engineer at Sun Microsystems, Inc. "ODMG's API is a valuable contribution for our enterprise developers because it provides portability across multiple database products. It also provides the standard for object-relational mapping in Java, and Sun is very pleased to endorse it."
The ODMG Binding for Java is part of ODMG 2.0, a recently published specification that defines ways for applications written in Java, C++ and SmallTalk to interact with object-oriented databases. An overview of the specification and the news release announcing its availability can be found on the web at http://www.odmg.org.
Sun's long-standing support of standards bodies extends to Sun's involvement in the ODMG. The Object Database Management Group was founded in 1991 by Rick Cattell, who now serves as its chair. ODMG is made up of more than 20 member companies.
Sun's endorsement of the ODMG API reinforces Sun's strong commitment to making available Java technologies and products for enterprise developers. At its annual JavaOne developer conference in April, Sun debuted its Java Platform for the Enterprise, including Enterprise JavaBeans. This initiative is aimed at taking the complexity out of building end-to-end business solutions in Java.
* Originally published in Novell AppNotes
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.