Jump to: navigation, search

Difference between revisions of "EclipseLink/Examples/JPA/ORMSessions"

Line 1: Line 1:
 
Sessions are a key component of the EclipseLink Server application— they provide EclipseLink with access to the database. Sessions enable you to execute queries, and they return persistent objects and other results for client applications.
 
Sessions are a key component of the EclipseLink Server application— they provide EclipseLink with access to the database. Sessions enable you to execute queries, and they return persistent objects and other results for client applications.
 
= Session Factory =
 
  
 
= Session Manager =
 
= Session Manager =
Line 30: Line 28:
 
Session session = manager.getSession("mysession", classLoader);
 
Session session = manager.getSession("mysession", classLoader);
 
</pre></code>
 
</pre></code>
 +
 +
= Session Factory =
 +
Helper class to simplify the development and generation of code that accesses EclipseLink through the SessionManager (sessions config XML).
 +
 +
Responsibilities:
 +
* Lookup of a session by name using default or provided sessions config location
 +
* Support lookup of active UnitOfWork and Session in JTA environments
 +
* Hot/Re-deployment handling of applications
 +
* Detachment helpers to simplify usage within a local session bean

Revision as of 11:02, 24 October 2007

Sessions are a key component of the EclipseLink Server application— they provide EclipseLink with access to the database. Sessions enable you to execute queries, and they return persistent objects and other results for client applications.

Session Manager

The EclipseLink session manager enables developers to build a series of sessions that are maintained under a single entity. The session manager is a static utility class that loads EclipseLink sessions from the sessions.xml file, caches the sessions by name in memory, and provides a single access point for EclipseLink sessions.

Loading a Session Manager Instance

import org.eclipse.persistence.tools.sessionmanagement.SessionManager;
SessionManager sessionManager = SessionManager.getManager();

EclipseLink uses a class loader to load the session manager. The session manager, in turn, uses that same class loader to load named sessions that are not already initialized in the session manager cache.

Loading a Named Session from Session Manager Using Defaults

/* This example loads a named session (mysession) defined in the sessions.xml file. */
SessionManager manager = SessionManager.getManager();
Server server = (Server) manager.getSession("myserversession");

Loading a Session with an Alternative Class Loader

You can use an alternative class loader to load sessions. This is common when your EclipseLink application integrates with a J2EE container. If the session is not already in the session manager's in-memory cache of sessions, the session manager creates the session and logs in.

/* This example uses the specified ClassLoader to load a session (mysession) defined in the sessions.xml file. */
ClassLoader classLoader = YourApplicationClass.getClassLoader();
SessionManager manager = SessionManager.getManager();
Session session = manager.getSession("mysession", classLoader);

Session Factory

Helper class to simplify the development and generation of code that accesses EclipseLink through the SessionManager (sessions config XML).

Responsibilities:

  • Lookup of a session by name using default or provided sessions config location
  • Support lookup of active UnitOfWork and Session in JTA environments
  • Hot/Re-deployment handling of applications
  • Detachment helpers to simplify usage within a local session bean