Skip to main content
Jump to: navigation, search

Difference between revisions of "Introduction to EclipseLink Development Tools (ELUG)"

m
m
Line 1: Line 1:
 
<div style="float:right;border:1px solid #000000;padding:5px">__TOC__
 
<div style="float:right;border:1px solid #000000;padding:5px">__TOC__
 
[[Special:Whatlinkshere/Introduction to EclipseLink Development Tools (ELUG)|Related Topics]]</div>
 
[[Special:Whatlinkshere/Introduction to EclipseLink Development Tools (ELUG)|Related Topics]]</div>
 
 
The EclipseLink runtime provides Java or Java EE applications with access to persistent entities stored in a data source. In addition to run-time capabilities, the EclispeLink Foundation Library includes the EclipseLink Application Programming Interface (API). This API enables applications to access EclipseLink run-time features.
 
The EclipseLink runtime provides Java or Java EE applications with access to persistent entities stored in a data source. In addition to run-time capabilities, the EclispeLink Foundation Library includes the EclipseLink Application Programming Interface (API). This API enables applications to access EclipseLink run-time features.
  
Line 10: Line 9:
 
* [[#EclipseLink_Run-Time_Environment|EclipseLink Run-Time Environment]]
 
* [[#EclipseLink_Run-Time_Environment|EclipseLink Run-Time Environment]]
  
EclipseLink metadata is the link between the two (see [[Introduction to EclipseLink Application Development (ELUG)|Working with EclipseLink Metadata]]).
+
EclipseLink metadata is the link between the two (see [[Introduction to EclipseLink Application Development (ELUG)#Working with EclipseLink Metadata|Working with EclipseLink Metadata]]).
  
 
The following figure illustrates how these elements interact with the data source.
 
The following figure illustrates how these elements interact with the data source.
Line 17: Line 16:
 
'''''EclipseLink Components in Development Lifecycle'''''
 
'''''EclipseLink Components in Development Lifecycle'''''
  
[[Image:under01.gif|EclipseLink Components in Development Lifecycle]]<br /><br />
+
[[Image:under01.gif|EclipseLink Components in Development Lifecycle]]
 +
 
 +
 
  
 
==Development Environment==
 
==Development Environment==
Line 25: Line 26:
  
 
<span id="Figure 3-2 "></span>
 
<span id="Figure 3-2 "></span>
'''''Workbench in Development Environment</font>'''''
+
'''''Workbench in Development Environment'''''
  
[[Image:under03.gif|Workbench in Development Environment]]<br /><br />
+
[[Image:under03.gif|Workbench in Development Environment]]
  
 
Workbench can import compiled entity classes (Java objects or EJB entity beans), as well as relational or nonrelational schemas through a JDBC driver (configured by you). Because EclipseLink imports the object and relational models for mapping, you can develop the two models relatively independently from the mapping phase of a project development.
 
Workbench can import compiled entity classes (Java objects or EJB entity beans), as well as relational or nonrelational schemas through a JDBC driver (configured by you). Because EclipseLink imports the object and relational models for mapping, you can develop the two models relatively independently from the mapping phase of a project development.
 +
 +
  
 
==EclipseLink Run-Time Environment==
 
==EclipseLink Run-Time Environment==

Revision as of 07:51, 5 December 2007

The EclipseLink runtime provides Java or Java EE applications with access to persistent entities stored in a data source. In addition to run-time capabilities, the EclispeLink Foundation Library includes the EclipseLink Application Programming Interface (API). This API enables applications to access EclipseLink run-time features.

EclipseLink includes additional development tools that simplify application development. These tools capture mapping and run-time configuration information in metadata files that EclipseLink passes to the application at run time.

This section includes the following sections:

EclipseLink metadata is the link between the two (see Working with EclipseLink Metadata).

The following figure illustrates how these elements interact with the data source.

EclipseLink Components in Development Lifecycle

EclipseLink Components in Development Lifecycle


Development Environment

To create a EclipseLink application, use the Workbench to map objects to data sources using relational and nonrelational models. Capture the resulting mappings and additional run-time configurations in the EclipseLink project file (project.xml) and build a session configuration file (sessions.xml). These files together represent your entire EclipseLink project, as shown in the following figure].

During development, you can use the EclipseLink API to define query and transaction logic. When you use entity beans, there is generally little or no direct use of the EclipseLink API and there is no session or sessions.xml file.

Workbench in Development Environment

Workbench in Development Environment

Workbench can import compiled entity classes (Java objects or EJB entity beans), as well as relational or nonrelational schemas through a JDBC driver (configured by you). Because EclipseLink imports the object and relational models for mapping, you can develop the two models relatively independently from the mapping phase of a project development.


EclipseLink Run-Time Environment

The EclispeLink Foundation Library provides the EclipseLink run-time component. Access the run-time component either directly through the EclipseLink API or indirectly through a Java EE container when using entity beans with container-managed persistence. The run-time environment is not a separate or external process–it is embedded within the application. Application calls invoke EclipseLink to provide persistence behavior. This function allows for transactional and thread-safe access to shared database connections and cached objects.

In addition to Java EE environments, EclipseLink fully supports non-Java EE environments as well. See Selecting an Architecture with EclipseLink for more information.



Copyright Statement

Back to the top