Difference between revisions of "EclipseLink/UserGuide/JPA/Basic JPA Development/Mapping/Locking"

From Eclipsepedia

Jump to: navigation, search
m
Line 16: Line 16:
  
 
If you are building a three-tier application, be aware of how that architecture affects the way you use locking (see [[Introduction%20to%20Descriptors%20(ELUG)#Locking in a Three-Tier Application|Locking in a Three-Tier Application]]).
 
If you are building a three-tier application, be aware of how that architecture affects the way you use locking (see [[Introduction%20to%20Descriptors%20(ELUG)#Locking in a Three-Tier Application|Locking in a Three-Tier Application]]).
 
For more information, see [[Introduction%20to%20Descriptors%20(ELUG)#Descriptors and Locking|Descriptors and Locking]].
 
  
  

Revision as of 11:01, 4 May 2011

EclipseLink JPA

link="http://wiki.eclipse.org/EclipseLink"
EclipseLink
Website
Download
Community
Mailing ListForumsIRC
Bugzilla
Open
Help Wanted
Bug Day
Contribute
Browse Source

Elug example icon.png Examples


Locking

This section describes choices you need to make when deciding on how to use EclipseLink locking options in your application architecture. We strongly recommend always using a locking policy in a concurrent system (see Configuring Locking Policy).

These choices can be summarized as follows:

If you are building a three-tier application, be aware of how that architecture affects the way you use locking (see Locking in a Three-Tier Application).



Eclipselink-logo.gif
Version: 2.2.0 DRAFT
Other versions...