Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/UserGuide/JPA/2.4/intro001"
m |
m |
||
| Line 5: | Line 5: | ||
|category=JPA | |category=JPA | ||
|release=2.4.x | |release=2.4.x | ||
| − | |title= }}<span class="metaname"> </span> | + | |title=TLJPA}} |
| + | <span class="metaname"> </span> | ||
{| class="simple oac_no_warn" width="100%" | {| class="simple oac_no_warn" width="100%" | ||
| Line 29: | Line 30: | ||
|} | |} | ||
| − | [[Image:Elug_draft_icon.png|Warning]]Beta Draft: 2012-06- | + | [[Image:Elug_draft_icon.png|Warning]]Beta Draft: 2012-06-18 |
<span id="CEGHCAJB"></span><span id="TLJPA303"></span> | <span id="CEGHCAJB"></span><span id="TLJPA303"></span> | ||
| Line 37: | Line 38: | ||
Using EclipseLink, 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. | Using EclipseLink, 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. | ||
| − | EclipseLink is suitable for use with a wide range of Java Enterprise Edition (Java EE) and Java application architectures | + | EclipseLink is suitable for use with a wide range of Java Enterprise Edition (Java EE) and Java application architectures. Use EclipseLink to design, implement, deploy, and optimize an advanced object-persistence and object-transformation layer that supports a variety of data sources and formats, including the following: ''assembly archives'', and manages deployment aspects of the software system contained therein. You create assembly archives in Oracle Virtual Assembly Builder Studio. |
* Relational–for transactional persistence of Java objects to a relational database accessed using Java Database Connectivity (JDBC) drivers. | * Relational–for transactional persistence of Java objects to a relational database accessed using Java Database Connectivity (JDBC) drivers. | ||
| Line 74: | Line 75: | ||
|} | |} | ||
| width="34%" align="center" | | | width="34%" align="center" | | ||
| − | [[Image:Eclipselink-logo.gif|150px|EclispeLink]]<br />[[Image:Elug_home_icon.png|EclipseLink logo]][http://www.eclipse.org/eclipselink/ EclipseLink Home]<br /> | + | [[Image:Eclipselink-logo.gif|150px|EclispeLink]]<br />[[Image:Elug_home_icon.png|EclipseLink logo]] [http://www.eclipse.org/eclipselink/ EclipseLink Home] • [[Image:Elug_pdf.png|PDF]] PDF (coming soon)<br /> |
| align="right" valign="bottom" | | | align="right" valign="bottom" | | ||
{| class="simple oac_no_warn" width="225" | {| class="simple oac_no_warn" width="225" | ||
Revision as of 10:07, 18 June 2012
|
|
Beta Draft: 2012-06-18
About EclipseLink
Using EclipseLink, 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.
EclipseLink is suitable for use with a wide range of Java Enterprise Edition (Java EE) and Java application architectures. Use EclipseLink to design, implement, deploy, and optimize an advanced object-persistence and object-transformation layer that supports a variety of data sources and formats, including the following: assembly archives, and manages deployment aspects of the software system contained therein. You create assembly archives in Oracle Virtual Assembly Builder Studio.
- Relational–for transactional persistence of Java objects to a relational database accessed using Java Database Connectivity (JDBC) drivers.
- Object-Relational Data Type–for transactional persistence of Java objects to special-purpose structured data source representations optimized for storage in object-relational data type databases such as Oracle Database.
- Enterprise information system (EIS)–for transactional persistence of Java objects to a non-relational data source accessed using a Java EE Connector architecture (JCA) adapter and any supported EIS record type, including indexed, mapped, or XML.
- XML–for non-transactional, non-prescription (in-memory) conversion between Java objects and XML Schema Document (XSD)-based XML documents using Java Architecture for XML Binding (JAXB).
EclipseLink includes support for EJB 3.0 and the Java Persistence API (JPA) in Java EE and Java SE environments including integration with a variety of application servers including:
- Oracle WebLogic Server
- Glassfish
- JBoss
- IBM WebSphere application server
- SAP NetWeaver
- Oracle OC4J
- various web containers (Apache Tomcat, IBM WebSphere CE, SpringSource tcServer)
EclipseLink lets you quickly capture and define object-to-data source and object-to-data representation mappings in a flexible, efficient metadata format (see Configuration).
The EclipseLink 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.
|
|
|
|
