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 (component-managed transactions where the bean manages transactions itself).
- Entity beans use container-managed transactions.
- Web components (servlets) and application client components use component-managed transactions.
Use the following tasks to develop WebSphere application components that use transactions:
- Set transactional deployment attributes. This task determines whether EJB components use container- or bean-managed transactions by setting an appropriate value on the Transaction type deployment attribute. We can also configure other transactional deployment descriptor attributes.
- Use component-managed transactions. If we want a session bean, Web component, or application client component to manage its own transactions, write the code that explicitly demarcates the boundaries of a transaction. There are some limitations to the transaction support available to application client components.
Configuring transactional deployment attributes
Use component-managed transactions
Related concepts
Transaction support in
Related tasks
Use the transaction service