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 |
|||
| 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]]). | ||
| − | |||
| − | |||
Revision as of 11:01, 4 May 2011
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 (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).
