Jump to: navigation, search

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

m (Locking)
m (Locking)
Line 1: Line 1:
 +
{{EclipseLink_Examples
 +
*|example = [[EclipseLink/Examples/JPA/Locking|Locking]]
 +
}}
 
=Locking=
 
=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%20a%20Descriptor%20(ELUG)#Configuring Locking Policy|Configuring Locking Policy]]).
 
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%20a%20Descriptor%20(ELUG)#Configuring Locking Policy|Configuring Locking Policy]]).

Revision as of 09:44, 16 June 2010

{{EclipseLink_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).

For more information, see Descriptors and Locking.



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