WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Developing components to use transactions

These topics provide information about developing WebSphere application components to use transactions

Why and when to perform this task

The way that applications use transactions depends on the type of application component, as follows:

You configure whether EJB components use container- or bean-managed transactions by setting an appropriate value on the Transaction type deployment attribute, as described in Configuring transactional deployment attributes. You can also configure other transactional deployment descriptor attributes.

If you want a session bean to manage its own transactions, you must write the code that explicitly demarcates the boundaries of a transaction as described in Using component-managed transactions.

If you want a Web component to use transactions, you must write the code that explicitly demarcates the boundaries of a transaction as described in Using component-managed transactions.

Similarly, if you want an application client component to use transactions, you must write the code that explicitly demarcates the boundaries of a transaction as described in Using component-managed transactions. There are some limitations to the transaction support available to application client components, as described in Client support for transactions.




Sub-topics
Configuring transactional deployment attributes
Using component-managed transactions

Related concepts
Transaction support in WebSphere Application Server

Related reference
UserTransaction interface - methods available

Task topic    

Terms of Use | Feedback

Last updated: Mar 17, 2005 4:28:29 AM CST
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tjta_devap.html

© Copyright IBM Corporation 2002, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)