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

From Eclipsepedia

Jump to: navigation, search
m
(Locking)
 
(5 intermediate revisions by one user not shown)
Line 1: Line 1:
{{EclipseLink_UserGuide|info=y|examples=y
+
{{EclipseLink_UserGuide
 +
|info=y
 +
|toc=n
 +
|eclipselink=y
 +
|eclipselinktype=JPA
 +
|examples=y
 
|example = *[[EclipseLink/Examples/JPA/Locking|Locking]]
 
|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.
  
 
These choices can be summarized as follows:
 
These choices can be summarized as follows:
Line 9: Line 15:
 
* Pessimistic Locking
 
* Pessimistic Locking
  
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).
 
+
For more information, see [[Introduction%20to%20Descriptors%20(ELUG)#Descriptors and Locking|Descriptors and Locking]].
+
  
  
Line 17: Line 21:
  
 
{{EclipseLink_JPA
 
{{EclipseLink_JPA
|previous= [[EclipseLink/UserGuide/JPA/Basic_JPA_Development/Mapping/Relationship_Mappings/Collection_Mappings/ManyToMany|ManyToMany]]
+
|previous= [[EclipseLink/UserGuide/JPA/Basic_JPA_Development/Mapping/Relationship_Mappings/Collection_Mappings/ManyToMany|Many-to-Many Mapping]]
 
|next=[[EclipseLink/UserGuide/JPA/Basic_JPA_Development/Mapping/Locking/Optimistic Locking|Optimistic Locking]]
 
|next=[[EclipseLink/UserGuide/JPA/Basic_JPA_Development/Mapping/Locking/Optimistic Locking|Optimistic Locking]]
|up=[[EclipseLink/UserGuide/JPA/Basic JPA Development/Mapping|Mapping]]}}
+
|up=[[EclipseLink/UserGuide/JPA/Basic JPA Development/Mapping|Mapping]]
 +
|version=2.2.0 DRAFT}}

Latest revision as of 11:14, 25 April 2012

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


[edit] 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.

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



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