TOP LINK
What is TopLink?
Oracle TopLink builds high-performance applications that store persistent object-oriented data in a relational database. It successfully transforms object-orien
Oracle TopLink builds high-performance applications that store persistent object-oriented data in a relational database. It successfully transforms object-orien
Figure 1–1 TopLink Runtime Architecture
Using TopLink, you can integrate persistence and object-transformation into your
application, while staying focused on your primary domain problem by taking advantage of an efficient, flexible, and field-proven solution (see "Solving the Object-Persistence Impedance Mismatch").
application, while staying focused on your primary domain problem by taking advantage of an efficient, flexible, and field-proven solution (see "Solving the Object-Persistence Impedance Mismatch").
TopLink is suitable for use with a wide range of Java 2 Enterprise Edition (J2EE) and Java application architectures (see "TopLink Application Architectures").
Use TopLink to design, implement, deploy, and optimize an advanced, object-persistence and object-transformation layer that supports a variety of data sources and formats, including:
■ Relational–for transactional persistence of Java objects to a relational database
accessed using Java Database Connectivity (JDBC) drivers.
■ Object-Relational–for transactional persistence of Java objects to special purpose
structured data source representations optimized for storage in object-relational
databases such as Oracle Database.
■ Enterprise information system (EIS)–for transactional persistence of Java objects to
a nonrelational data source accessed using a J2EE Connector architecture (J2C)
adapter, and any supported EIS record type, including indexed, mapped, or XML.
■ XML–for nontransactional, nonpersistent (in-memory) conversion between Java
objects and XML Schema Document (XSD) based XML documents, using Java
Architecture for XML Binding (JAXB).
TopLink includes support for container-managed persistence (CMP) containers from a variety of vendors–such as Oracle Containers for J2EE (OC4J), IBM WebSphere application server, and BEA WebLogic Server–and support for base classes that simplify bean-managed persistence (BMP) development.
The extensive suite of development tools that TopLink provides, including Oracle
TopLink Workbench, lets you quickly capture and define object-to-data source and
object-to-data representation mappings in a flexible, efficient metadata format (see "Understanding TopLink Metadata" ).
The TopLink runtime lets your application exploit this mapping metadata with a simple session facade that provides in-depth support for data access, queries, transactions (both with and without an external transaction controller), and caching.
Solving the Object-Persistence Impedance Mismatch
Java-to-data source integration is a widely underestimated problem when creating enterprise Java applications. This complex problem involves more than simply reading from and writing to a data source.
The data source elements include tables, rows, columns, and primary and foreign keys. The Java and J2EE include entity classes (regular Java classes or Enterprise JavaBeans (EJB) entity beans), business rules, complex relationships, and inheritance. In a nonrelational data source, you must match your Java entities with EIS records or XML elements and schemas.
These differences (as shown in Figure 1–2) are known as the object-persistence impedance mismatch.
Java-to-data source integration is a widely underestimated problem when creating enterprise Java applications. This complex problem involves more than simply reading from and writing to a data source.
The data source elements include tables, rows, columns, and primary and foreign keys. The Java and J2EE include entity classes (regular Java classes or Enterprise JavaBeans (EJB) entity beans), business rules, complex relationships, and inheritance. In a nonrelational data source, you must match your Java entities with EIS records or XML elements and schemas.
These differences (as shown in Figure 1–2) are known as the object-persistence impedance mismatch.
Figure 1–2 Solving Object-Persistence Impedance Mismatch
Successful solution requires bridging these different technologies, and solving the
object-persistence impedance mismatch–a challenging and resource-intensive
problem. To solve this problem, you must resolve the following issues between J2EE and data source elements:
■ Fundamentally different technologies
■ Different skill sets
■ Different staff and ownership for each of the technologies
■ Different modeling and design principles
Application developers need a product that enables them to integrate Java applications with any data source, without compromising ideal application design or data integrity. In addition, Java developers need the ability to store (that is, persist) and retrieve business domain objects using a relational database or a nonrelational data source as a repository.
object-persistence impedance mismatch–a challenging and resource-intensive
problem. To solve this problem, you must resolve the following issues between J2EE and data source elements:
■ Fundamentally different technologies
■ Different skill sets
■ Different staff and ownership for each of the technologies
■ Different modeling and design principles
Application developers need a product that enables them to integrate Java applications with any data source, without compromising ideal application design or data integrity. In addition, Java developers need the ability to store (that is, persist) and retrieve business domain objects using a relational database or a nonrelational data source as a repository.
TopLink Solution
TopLink addresses the disparity between Java objects and data sources. TopLink is a persistence framework that manages relational, object-relational, EIS, and XML mappings in a seamless manner.
This allows developers to rapidly build applications that combine the best aspects of object technology and the specific data source.
TopLink enables you to do the following:
■ Persist Java objects to virtually any relational database supported by a
JDBC-compliant driver.
■ Persist Java objects to virtually any nonrelational data source supported by a J2EE Connector architecture (J2C) adapter using indexed, mapped, or XML enterprise information system (EIS) records.
■ Perform in-memory conversions between Java objects and XML Schema (XSD)
based XML documents using JAXB.
■ Map any object model to any relational or nonrelational schema, using the Oracle TopLink Workbench graphical mapping tool.
■ Use TopLink successfully, even if you are unfamiliar with SQL or JDBC, because
TopLink offers a clear, object-oriented view of data sources.
TopLink addresses the disparity between Java objects and data sources. TopLink is a persistence framework that manages relational, object-relational, EIS, and XML mappings in a seamless manner.
This allows developers to rapidly build applications that combine the best aspects of object technology and the specific data source.
TopLink enables you to do the following:
■ Persist Java objects to virtually any relational database supported by a
JDBC-compliant driver.
■ Persist Java objects to virtually any nonrelational data source supported by a J2EE Connector architecture (J2C) adapter using indexed, mapped, or XML enterprise information system (EIS) records.
■ Perform in-memory conversions between Java objects and XML Schema (XSD)
based XML documents using JAXB.
■ Map any object model to any relational or nonrelational schema, using the Oracle TopLink Workbench graphical mapping tool.
■ Use TopLink successfully, even if you are unfamiliar with SQL or JDBC, because
TopLink offers a clear, object-oriented view of data sources.
TopLink Key Features
TopLink provides an extensive and thorough set of features. Java developers can use these features to rapidly build high-performance enterprise applications that are both scalable and maintainable.
Some of the primary features of TopLink are the following:
■ Nonintrusive, flexible, metadata-based architecture (see "Understanding TopLink
Metadata")
■ Comprehensive visual TopLink Workbench
■ Advanced mapping support and flexibility (relational, object-relational, EIS, and XML)
■ Object caching support
■ Query flexibility
■ Just-in-time reading
■ Caching
■ Object-level transaction support and integration
■ Locking
■ Multiple performance tuning options
■ Architectural flexibility
For additional information, see the TopLink page on OTN:
http://www.oracle.com/technology/products/ias/toplink/index.html
TopLink provides an extensive and thorough set of features. Java developers can use these features to rapidly build high-performance enterprise applications that are both scalable and maintainable.
Some of the primary features of TopLink are the following:
■ Nonintrusive, flexible, metadata-based architecture (see "Understanding TopLink
Metadata")
■ Comprehensive visual TopLink Workbench
■ Advanced mapping support and flexibility (relational, object-relational, EIS, and XML)
■ Object caching support
■ Query flexibility
■ Just-in-time reading
■ Caching
■ Object-level transaction support and integration
■ Locking
■ Multiple performance tuning options
■ Architectural flexibility
For additional information, see the TopLink page on OTN:
http://www.oracle.com/technology/products/ias/toplink/index.html
0 comments
Post a Comment