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/Transactions (ELUG)"
< EclipseLink | UserGuide
m (related topics link) |
m (→Transactions) |
||
Line 1: | Line 1: | ||
=Transactions= | =Transactions= | ||
− | + | The following sections describe how to use the EclipseLink unit of work to transactionally perform create, read, update, and delete operations with and without an external transaction processor: | |
− | *[[Introduction to EclipseLink Transactions (ELUG)]] | + | *[[Introduction to EclipseLink Transactions (ELUG)]] - describes how to use the unit of work, the EclipseLink wrapper for a transaction, and how EclipseLink integrates with transaction management and other important query concepts. |
− | + | ||
− | *[[Using Basic Unit of Work API (ELUG)]] | + | *[[Using Basic Unit of Work API (ELUG)]] - explains the essential unit of work API calls that you are most likely to use throughout the development cycle. |
− | + | ||
− | *[[Using Advanced Unit of Work API (ELUG)]] | + | *[[Using Advanced Unit of Work API (ELUG)]] - explains the advanced unit of work API calls that you may use. |
− | + | ||
Revision as of 11:02, 11 December 2007
Transactions
The following sections describe how to use the EclipseLink unit of work to transactionally perform create, read, update, and delete operations with and without an external transaction processor:
- Introduction to EclipseLink Transactions (ELUG) - describes how to use the unit of work, the EclipseLink wrapper for a transaction, and how EclipseLink integrates with transaction management and other important query concepts.
- Using Basic Unit of Work API (ELUG) - explains the essential unit of work API calls that you are most likely to use throughout the development cycle.
- Using Advanced Unit of Work API (ELUG) - explains the advanced unit of work API calls that you may use.