Notice: this Wiki will be going read only early in 2024 and edits will no longer be 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 (→Locking) |
(→Locking) |
||
(4 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
− | |||
− | |||
− | |||
{{EclipseLink_UserGuide | {{EclipseLink_UserGuide | ||
|info=y | |info=y | ||
|toc=n | |toc=n | ||
|eclipselink=y | |eclipselink=y | ||
− | |eclipselinktype=JPA}} | + | |eclipselinktype=JPA |
+ | |examples=y | ||
+ | |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 | + | 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 14: | 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 | + | If you are building a three-tier application, be aware of how that architecture affects the way you use locking). |
− | + | ||
− | + | ||
Line 22: | Line 21: | ||
{{EclipseLink_JPA | {{EclipseLink_JPA | ||
− | |previous= [[EclipseLink/UserGuide/JPA/Basic_JPA_Development/Mapping/Relationship_Mappings/Collection_Mappings/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}} | |version=2.2.0 DRAFT}} |
Latest revision as of 11:14, 25 April 2012
EclipseLink JPA
EclipseLink | |
Website | |
Download | |
Community | |
Mailing List • Forums • IRC • mattermost | |
Issues | |
Open • Help Wanted • Bug Day | |
Contribute | |
Browse Source |
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.
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).