Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/UserGuide/JPA/Basic JPA Development/Mapping/Locking"
< EclipseLink | UserGuide | JPA | Basic JPA Development | Mapping
m |
m (→Locking) |
||
Line 2: | Line 2: | ||
|example = *[[EclipseLink/Examples/JPA/Locking|Locking]] | |example = *[[EclipseLink/Examples/JPA/Locking|Locking]] | ||
}} | }} | ||
+ | {{EclipseLink_UserGuide | ||
+ | |info=y | ||
+ | |toc=n | ||
+ | |eclipselink=y | ||
+ | |eclipselinktype=JPA}} | ||
=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]]). | ||
Line 19: | Line 24: | ||
|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|ManyToMany]] | ||
|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}} |
Revision as of 15:37, 12 January 2011
EclipseLink | |
Website | |
Download | |
Community | |
Mailing List • Forums • IRC • mattermost | |
Issues | |
Open • Help Wanted • Bug Day | |
Contribute | |
Browse Source |
Examples
EclipseLink JPA
EclipseLink | |
Website | |
Download | |
Community | |
Mailing List • Forums • IRC • mattermost | |
Issues | |
Open • Help Wanted • Bug Day | |
Contribute | |
Browse Source |
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:
- Optimistic Locking
- Pessimistic Locking
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.