|
Oracle TopLink Developer's Guide
10g Release 3 (10.1.3) B13593-01 |
|
 Previous |
 Next |
|
Oracle TopLink Developer's Guide
10g Release 3 (10.1.3) B13593-01 |
|
|
Previous |
Next |
When you design your application, you must choose how and where to use TopLink. You can use TopLink to perform a variety of persistence and data transformation functions (see "Understanding TopLink Usage") on a variety of Java-supporting platforms (see "Understanding Target Platforms"). When you design your application architecture, keep these capabilities in mind (see "Selecting an Architecture With TopLink").
This section describes the basic ways in which you can use TopLink, including the following usage types:
You can use TopLink to persist Java objects to relational databases that support SQL data types accessed using JDBC.
For more information, see "Building Relational Projects for a Relational Database".
You can use TopLink to persist Java objects to object-relational databases that support data types specialized for object storage (such as Oracle Database) accessed using JDBC.
For more information, see "Building Relational Projects for an Object-Relational Database".
You can use TopLink to persist XML documents to an Oracle XML database using TopLink direct-to-XMLType mappings.
For more information, see "Relational Projects" and "Direct to XMLType Mapping".
You can use TopLink to persist Java objects to an EIS data source using a J2C adapter.
In this scenario, the application invokes EIS data source-defined operations by sending EIS interactions to the J2C adapter. Operations can take (and return) EIS records. Using TopLink EIS descriptors and mappings, you can easily map Java objects to the EIS record types supported by your J2C adapter and EIS data source.
This usage is common in applications that connect to legacy data sources and is also applicable to Web services.
For more information, see "EIS Projects".
You can use TopLink for in-memory, nonpersistent Java object-to-XML transformation with XML Schema (XSD) based XML documents and JAXB.
You can use the TopLink JAXB compiler with your XSD to generate both JAXB-specific artifacts (such as content and element interfaces, implementation classes, and object factory class) and TopLink-specific artifacts (such as sessions and project XML files and TopLink Workbench project). For more information, see "TopLink Support for Java Architecture for XML Binding (JAXB)").
This usage has many applications, including messaging and Web services.
For more information, see "XML Projects".
TopLink supports any enterprise architecture that uses Java, including the following:
Java application servers and J2EE containers, such as Oracle Application Server and Oracle Containers for J2EE (OC4J)
Java-supporting databases, such as Oracle Database
Java-compatible browsers, such as Netscape and Internet Explorer
Server Java platforms, such as AS/400, OS/390, and UNIX
Application packaging requirements of the specific target platform (for deployment in the host Java or J2EE environment) influences how developers use and configure TopLink. For example, developers package a J2EE application in an Enterprise Archive (EAR) file. Within the EAR file, there are several ways to package persistent entities within Web Archive (WAR) and Java Archive (JAR). How developers configure TopLink depends, in part, on how they package the application and how they use the host application server class loader.
In addition, TopLink provides custom CMP integration for a variety of application servers.
For detailed information about supported application server versions, custom integration, and configuration requirements, see "Integrating TopLink With an Application Server ".
