The Status interface defines static variables used for transaction status codes.
The transaction manager supports a synchronization mechanism that allows the interested party to be notified before and after the transaction completes.
The Transaction interface allows operations to be performed against the transaction in the target Transaction object.
The TransactionManager interface defines the methods that allow an application server to manage transaction boundaries.
This interface is intended for use by system level application server components such as persistence managers, resource adapters, as well as Jakarta Enterprise Beans and Web application components.
The UserTransaction interface defines the methods that allow an application to explicitly manage transaction boundaries.
The TxType element of the annotation indicates whether a bean method is to be executed within a transaction context where the values provide the following corresponding behavior.
This exception is thrown by the rollback operation on a resource to report that a heuristic decision was made and that all relevant updates have been committed.
This exception is thrown to report that a heuristic decision was made and that some relevant updates have been committed and others have been rolled back.
This exception is thrown by the commit operation to report that a heuristic decision was made and that all relevant updates have been rolled back.
This exception indicates that the request carried an invalid transaction context.
NotSupportedException exception indicates that the request cannot be executed because the operation is not a supported feature.
RollbackException exception is thrown when the transaction has been marked for rollback only or the transaction has been rolled back instead of committed.
The SystemException is thrown by the transaction manager to indicate that it has encountered an unexpected error condition that prevents future transaction services from proceeding.
The TransactionalException thrown from the Transactional interceptors implementation contains the original exception as its nested exception and is a RuntimeException, therefore, by default any transaction that was started as a result of a Transactional annotation earlier in the call stream will be marked for rollback as a result of the TransactionalException being thrown by the Transactional interceptor of the second bean.
This exception indicates that a request carried a null transaction context, but the target object requires an active transaction.
This exception indicates that the transaction associated with processing of the request has been rolled back, or it has been marked to roll back.
The jakarta.transaction.Transactional annotation provides the application the ability to declaratively control transaction boundaries on CDI managed beans, as well as classes defined as managed beans by the Jakarta EE specification, at both the class and method level where method level annotations override those at the class level.
The jakarta.transaction.TransactionScoped annotation provides the ability to specify a standard CDI scope to define bean instances whose lifecycle is scoped to the currently active Jakarta Transactions transaction.