|
|
This section includes the following topics:
This section describes how to integrate transactions in Enterprise JavaBeans (EJBs) applications that run under BEA WebLogic Server.
Before you begin, you should read Introducing Transactions, particularly the following topics:
This document describes the BEA WebLogic Server implementation of transactions in Enterprise JavaBeans. The information in this document supplements the Enterprise JavaBeans Specification 2.1, published by Sun Microsystems, Inc.
| Note: | Before proceeding with the rest of this chapter, you should be familiar with the contents of the EJB Specification 2.1 document, particularly the concepts and material presented in Chapter 16, “Support for Transactions.” |
For information about implementing Enterprise JavaBeans in WebLogic Server applications, see Programming WebLogic Enterprise JavaBeans.
The following general guidelines apply when implementing transactions in EJB applications for WebLogic Server:
For general guidelines about the WebLogic Server Transaction Service, see Capabilities and Limitations.
This section includes the following sections:
Transaction attributes determine how transactions are managed in EJB applications. For each EJB, the transaction attribute specifies whether transactions are demarcated by the WebLogic Server EJB container (container-managed transactions) or by the EJB itself (bean-managed transactions). The setting of the transaction-type element in the deployment descriptor determines whether an EJB is container-managed or bean-managed. See Chapter 16, “Support for Transactions,” and Chapter 21, “Deployment Descriptor,” in the EJB Specification 2.1, for more information about the transaction-type element.
In general, the use of container-managed transactions is preferred over bean-managed transactions because application coding is simpler. For example, in container-managed transactions, transactions do not need to be started explicitly.
WebLogic Server fully supports method-level transaction attributes as defined in Section 16.4 in the EJB Specification 2.1.
For container-managed transactions, the transaction attribute is specified in the container-transaction element in the deployment descriptor. Container-managed transactions include all entity beans and any stateful or stateless session beans with a transaction-type set to Container. For more information about these elements, see Programming WebLogic Server Enterprise JavaBeans.
The Application Assembler can specify the following transaction attributes for EJBs and their business methods:
For a detailed explanation about how the WebLogic Server EJB container responds to the trans-attribute setting, see section 17.6.2 in the
EJB Specification 2.1.
The WebLogic Server EJB container automatically sets the transaction timeout if a timeout value is not defined in the deployment descriptor. The container uses the value of the Timeout Seconds configuration parameter. The default timeout value is 30 seconds.
For EJBs with container-managed transactions, the EJBs have no access to the javax.transaction.UserTransaction interface, and the entering and exiting transaction contexts must match. In addition, EJBs with container-managed transactions have limited support for the setRollbackOnly and getRollbackOnly methods of the javax.ejb.EJBContext interface, where invocations are restricted by rules specified in Sections 16.4.4.2 and 16.4.4.3 of the EJB Specification 2.1.
For bean-managed transactions, the bean specifies transaction demarcations using methods in the javax.transaction.UserTransaction interface. Bean-managed transactions include any stateful or stateless session beans with a transaction-type set to Bean. Entity beans cannot use bean-managed transactions.
For stateless session beans, the entering and exiting transaction contexts must match. For stateful session beans, the entering and exiting transaction contexts may or may not match. If they do not match, the WebLogic Server EJB container maintains associations between the bean and the nonterminated transaction.
Session beans with bean-managed transactions cannot use the setRollbackOnly and getRollbackOnly methods of the javax.ejb.EJBContext interface.
When the EJB Specification 2.1 uses the phrase “participating in a transaction,” BEA interprets this to mean that the bean meets either of the following conditions:
This topic contains the following sections:
The EJB Specification 2.1 describes semantics that govern transaction processing behavior based on the EJB type (entity bean, stateless session bean, or stateful session bean) and the transaction type (container-managed or bean-managed). These semantics describe the transaction context at the time a method is invoked and define whether the EJB can access methods in the javax.transaction.UserTransaction interface. EJB applications must be designed with these semantics in mind.
For container-managed transactions, transaction semantics vary for each bean type.
Table 8-1 describes the transaction semantics for stateful session beans in container-managed transactions.
Table 8-2 describes the transaction semantics for stateless session beans in container-managed transactions.
Table 8-3 describes the transaction semantics for entity beans in container-managed transactions.
For bean-managed transactions, the transaction semantics differ between stateful and stateless session beans. For entity beans, transactions are never bean-managed.
Table 8-4 describes the transaction semantics for stateful session beans in bean-managed transactions.
Table 8-5 describes the transaction semantics for stateless session beans in bean-managed transactions.
A stateful session bean using container-managed transactions can implement the javax.ejb.SessionSynchronization interface to provide transaction synchronization notifications. In addition, all methods on the stateful session bean must support one of the following transaction attributes: REQUIRES_NEW, MANDATORY or REQUIRED. For more information about the javax.ejb.SessionSynchronization interface, see Section 6.5.3 in the EJB Specification 2.1.
If a bean implements SessionSynchronization, the WebLogic Server EJB container will typically make the following callbacks to the bean during transaction commit time:
The EJB container can call other beans or involve additional XA resources in the beforeCompletion method. The number of calls is limited by the beforeCompletionIterationLimit attribute. This attribute specifies how many cycles of callbacks are processed before the transaction is rolled back. A synchronization cycle can occur when a registered object receives a beforeCompletion callback and then enlists additional resources or causes a previously synchronized object to be reregistered. The iteration limit ensures that synchronization cycles do not run indefinitely.
Bean providers can specify the timeout period for transactions in EJB applications. If the duration of a transaction exceeds the specified timeout setting, then the Transaction Service rolls back the transaction automatically.
| Note: | You must set the timeout before you begin() the transaction. Setting a timeout does not affect transaction transactions that have already begun. |
Timeouts are specified according to the transaction type:
trans-timeout-seconds attribute in the weblogic-ejb-jar.xml deployment descriptor. For more information, see the Administration Guide.The Bean Provider should configure the trans-timeout-seconds attribute in the weblogic-ejb-jar.xml deployment descriptor.
UserTransaction.setTransactionTimeout method.
WebLogic Server EJB applications need to catch and handle specific exceptions thrown during transactions. For detailed information about handling exceptions, see Chapter 17, “Exception Handling,” in the EJB Specification 2.1 published by Sun Microsystems, Inc.
For more information about how exceptions are thrown by business methods in EJB transactions, see the following tables in Section 17.3: Table 12 (for container-managed transactions) and Table 13 (for bean-managed transactions).
For a client’s view of exceptions, see Section 17.4, particularly Section 12.4.1 (application exceptions), Section 17.4.2 (java.rmi.RemoteException), Section 17.4.2.1 (javax.transaction.TransactionRolledBackException), and Section 17.4.2.2 (javax.transaction.TransactionRequiredException).
|