TOC
Feedback
|
Home TOC |
|
Search
Feedback |
Transactions
by Dale Green
A typical enterprise application accesses and stores information in one or more databases. Because this information is critical for business operations, it must be accurate, current, and reliable. Data integrity would be lost if multiple programs were allowed to simultaneously update the same information. Also, it would be lost if a system that failed while processing a business transaction were to leave the affected data only partially updated. By preventing both of these scenarios, software transactions ensure data integrity. Transactions control the concurrent access of data by multiple programs. In the event of a system failure, transactions make sure that after recovery the data will be in a consistent state.
Note: Currently, this chapter discusses transactions only for enterprise beans. Subsequent versions will also discuss transactions for web components.
- What is a Transaction?
- Container-Managed Transactions
- Transaction Attributes
- Rolling Back a Container-Managed Transaction
- Synchronizing a Session Bean's Instance Variables
- Methods Not Allowed in Container-Managed Transactions
- Bean-Managed Transactions
- JDBC Transactions
- JTA Transactions
- Returning Without Committing
- Methods Not Allowed in Bean-Managed Transactions
- Summary of Transaction Options
- Transaction Timeouts
- Isolation Levels
- Updating Multiple Databases
|
Home TOC |
|
Search
Feedback |