Introduction
Oracle TopLink 11g R1 (11.1.1.1.0) offers a significant set
of new features based on the inclusion of the EclipseLink project along
with improved Oracle Coherence integration in the TopLink Grid feature.
This document describes the Oracle TopLink features in 11g in the following areas:
This release is based on the features delivered in Oracle
TopLink 11g (11.1.1.0.0).
EclipseLink
Oracle TopLink 11gR1 upgrades its core persistence functionality
including EclipseLink 1.1.1. This includes the following features
and enhancements:
JPA Enhancements
The upgrade of Oracle TopLink's JPA implementation from EclipseLink
1.0.2 to 1.1.1 includes a number of minor enhancements and new features
including:
Service Data Objects
This release includes EclipseLink 1.1.1's Service Data Objects (SDO)
implementation which supports both SDO 2.1.0 and 2.1.1 applications.
EclipseLink SDO is the reference implementation for SDO 2.1.1 as defined
in JSR 235. Within the Oracle WebLogic Server users will have out
of the box usage of SDO 2.1.0.
The EclipseLink SDO implementation enables Java developer to efficiently
build and use data object models that can be incorporated into service
architectures. It supports both dynamic and static SDO (through a
schema compiler) application development. In addition, EclipseLink
SDO has support for persisting SDOs with JPA to relational databases.
Data objects can be queried from a database with JPQL, marhalled across
the network, modified, returned to the server, and changes applied
to the database. EclipseLink SDO and JPA provide an integrated solution
for SCA applications with relational storage requirements.
Database Webservices
The first edition of EclipseLink DBWS included in this release allows
developers to build JAX-WS web services that provide access to relational
database data, stored procedures, and Oracle PL\SQL. DBWS web services
can be generated directly from relational metadata or SQL statements.
DBWS leverages the advanced object-relational (O/R) mapping and object-XML
(O/X) binding features of EclipseLink to provide xml-relational (X/R)
data access. DBWS generated web services can be customized to meet
specific application requirements.
Backwards Compatibility
This release continues to ship the original TopLink packaged in the
oracle.toplink.* packages, OC4J integration, and Mapping Workbench.
This will allow existing customers to continue to use TopLink as they
always have with minimal intrusion upgrading to 11gR1. These
libraries include:
-
/jlib/toplink.jar
- /jlib/toplink-oc4j.jar
- /jlib/toplink-src.zip
- /utils/workbench/*
These libraries and functionality will continue to be shipped in this
major release and its associated patch-sets. Customers are encouraged
to upgrade to the EclipseLink libraries and migrate to the software
in the org.eclipse.persistence.* packages to take advantage of future
improvements and new features.
WebLogic Integration
Within this coordinated release of the 11gR1
Oracle WebLogic Server and Suite customers will find Oracle TopLink
11gR1 included as a pre-packaged module within the container.
With TopLink being Oracle's strategic direction for persistence customers
can now easily deploy their applications using EclipseLink JPA, MOXy,
SDO, and DBWS to the WebLogic container without requiring the installation
of any additional libraries. Customers using the original TopLink
packages (oracle.toplink.*) will also find these available in the
same module.
JPA in WebLogic
In order to use the TopLink provided EclipseLink JPA
implementation develelopers simply need to specify EclipseLink as
their JPA provider in their application's persistence.xml file.
<provider>org.eclipse.persistence.jpa.PeristenceProvider</provider> |
Customers migrating from TopLink Essentials will find
that the EclipseLink JPA implementation offers the same (and more)
functionality. Migration requires only a minor process to switch from toplink.* persistence
unit property and query hint names.
TopLink Grid
This release also includes the second edition of TopLink
Grid. TopLink Grid offers an innovative integration between EclipseLink
JPA and Oracle's Coherence product which supports a range of configurations
from the use of Coherence as a distributed L2 Entity cache to the
use of Coherence as the primary data source. As an L2 cache, Coherence
supports caching very large numbers of Entities through the aggregation
of all cluster member heaps. As a data source, TopLink Grid will direct
all read, write, update, and query operations to Coherence. This configuration
supports highly available and responsive JPA applications with asynchrounous
database write behind.
The 11gR1 release of TopLink Grid introduces support
for persisting relationships. Now, Entities with either eager or lazy
relationships can be stored in Coherence. With the addition of this
feature most JPA applications can easily leverage the power of Coherence.
See the TopLink Grid page on OTN for details.
|
Bookmark
