Develop components to use transactions
These topics provide information about developing WebSphere application components to use transactions
The way that applications use transactions depends on the type of application component, as follows...
- A session bean can either use container-managed transactions (where the bean delegates management of transactions to the container) or bean-managed transactions (where the bean manages transactions itself).
- Entity beans use container-managed transactions.
- Web components (servlets) use bean-managed transactions.
You configure whether a component uses container- or bean-managed transactions by setting an appropriate value on the Transaction type deployment attribute, as described in Configuring transactional deployment attributes using the Assembly Toolkit. You can also configure other transactional deployment descriptor attributes.
If you want a session bean to manage its own transactions, write the code that explicitly demarcates the boundaries of a transaction as described in Using bean-managed transactions.
Similarly, if you want a Web component to use transactions, write the code that explicitly demarcates the boundaries of a transaction as described in Using bean-managed transactions.
See AlsoTransaction support in WAS
UserTransaction interface - methods available