Oracle® TopLink Developer's Guide 10g Release 3 (10.1.3.1.0) Part Number B28218-01 |
|
|
View PDF |
This chapter includes the following sections:
By design, TopLink can adapt to a variety of relational and nonrelational data sources.
To integrate TopLink with a data source that is not directly supported by the TopLink API, Oracle recommends that you use an EIS project (see "EIS Projects") or a XML project (see "XML Projects").
Using an EIS project, you can integrate your TopLink-enabled application with any nonrelational data source that supports a J2C) adapter and any supported EIS record type, including indexed, mapped, or XML. If no J2C adapter exists for your target data source, you can concentrate your integration efforts on creating an adapter. Simultaneously, you can build your application according to J2C specifications. Although this still requires custom development effort, it is more efficient than trying to extend TopLink classes and provides you with a J2C adapter that you can leverage in any other project (making it a better value).
Using an XML project, you can integrate your TopLink-enabled application with Web services or other XML-message based designs.
The remainder of this chapter describes other customization options provided by the TopLink API.
TopLink provides support for all the most common Java data types. Table 12-1 lists the TopLink mapping extensions that you can use to support custom data types. You can also create your object converter to allow conversion between a data type and your own Java type.
Table 12-1 Mapping Extensions for Custom Data Types