You can also choose to not manage the resource access transactions. You can use this method to reduce the cost of transaction management when the resources are only referenced.
The following figure shows the sequence when transactions are not used.
Figure 3-16 Sequence when transactions are not used
![[Figure]](figure/zu031500.gif)
Remember the following points when you do not use transactions:
- Transactions are not used when you specify Container in the <transaction-type> tag and specify either NotSupported or Never in the <trans-attribute> tag of the Enterprise Bean DD. You can also specify the definition in an annotation without using the DD. For details on the transaction attributes, see 2.7.3 CMT in the uCosminexus Application Server EJB Container Functionality Guide. For details on annotations, see 2. Annotations and Dependency Injection supported by Application Server in the uCosminexus Application Server API Reference Guide.
- Transactions are not used when you specify Bean in the <transaction-type> tag of the Enterprise Bean DD, and invoke the begin method of the UserTransaction object. You can also specify the definition in an annotation without using the DD. For details on annotations, see 2. Annotations and Dependency Injection supported by Application Server in the uCosminexus Application Server API Reference Guide.
- Transactions are not used when the begin method of the UserTransaction object is invoked by servlets and JSPs.
- You can also choose to manage the access to a specific resource adapter without using transactions. To realize this, set the transaction support level of the resource adapter that will not be managed using transactions to NoTransaction. The transactions are not managed for a resource adapter with the transaction support level NoTransaction even if the resource is accessed after the transaction starts.