All Downloads are FREE. Search and download functionalities are using the official Maven repository.

jakarta.transaction.Transactional Maven / Gradle / Ivy

Go to download

This artifact provides a single jar that contains all classes required to use remote EJB and JMS, including all dependencies. It is intended for use by those not using maven, maven users should just import the EJB and JMS BOM's instead (shaded JAR's cause lots of problems with maven, as it is very easy to inadvertently end up with different versions on classes on the class path).

The newest version!
/*
 * Copyright (c) 2013, 2020 Oracle and/or its affiliates. All rights reserved.
 *
 * This program and the accompanying materials are made available under the
 * terms of the Eclipse Public License v. 2.0, which is available at
 * http://www.eclipse.org/legal/epl-2.0.
 *
 * This Source Code may also be made available under the following Secondary
 * Licenses when the conditions for such availability set forth in the
 * Eclipse Public License v. 2.0 are satisfied: GNU General Public License,
 * version 2 with the GNU Classpath Exception, which is available at
 * https://www.gnu.org/software/classpath/license.html.
 *
 * SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0
 */

package jakarta.transaction;

import jakarta.enterprise.util.Nonbinding;
import jakarta.interceptor.InterceptorBinding;
import java.lang.annotation.*;

/**
 * 

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.

*

See the Jakarta Enterprise Beans specification for restrictions on the use of @Transactional with Jakarta Enterprise Beans.

*

This support is provided via an implementation of CDI interceptors that conduct the * necessary suspending, resuming, etc. The Transactional interceptor interposes on business method * invocations only and not on lifecycle events. Lifecycle methods are invoked in an unspecified * transaction context.

*

If an attempt is made to call any method of the UserTransaction interface from within the * scope of a bean or method annotated with @Transactional and a Transactional.TxType other than * NOT_SUPPORTED or NEVER, an IllegalStateException must be thrown. The use of the UserTransaction * is allowed within life cycle events. The use of the TransactionSynchronizationRegistry is allowed * regardless of any @Transactional annotation.

*

The Transactional interceptors must have a priority of * Interceptor.Priority.PLATFORM_BEFORE+200. * Refer to the Interceptors specification for more details.

*

The TxType element of the annotation indicates whether a bean method is to be executed within * a transaction context. TxType.REQUIRED is the default.

* *

By default checked exceptions do not result in the transactional interceptor marking the * transaction for rollback and instances of RuntimeException and its subclasses do. This default * behavior can be modified by specifying exceptions that result in the interceptor marking the * transaction for rollback and/or exceptions that do not result in rollback.

*

The rollbackOn element can be set to indicate exceptions that must cause the interceptor to mark * the transaction for rollback.

*

Conversely, the dontRollbackOn element can be set to indicate * exceptions that must not cause the interceptor to mark the transaction for rollback.

*

When a class is specified for either of these elements, the designated behavior applies to subclasses * of that class as well. If both elements are specified, dontRollbackOn takes precedence.

* * @version Jakarta Transactions 2.0 * @since JTA 1.2 */ @Inherited @InterceptorBinding @Target({ElementType.TYPE, ElementType.METHOD}) @Retention(value = RetentionPolicy.RUNTIME) public @interface Transactional { /** * The TxType element of the Transactional annotation indicates whether a bean method * is to be executed within a transaction context. * @return TxType element */ TxType value() default TxType.REQUIRED; /** * 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. * * @version Jakarta Transactions 2.0 */ public enum TxType { /** *

If called outside a transaction context, the interceptor must begin a new * Jakarta Transactions transaction, the managed bean method execution must then continue * inside this transaction context, and the transaction must be completed by * the interceptor.

*

If called inside a transaction context, the managed bean * method execution must then continue inside this transaction context.

*/ REQUIRED, /** *

If called outside a transaction context, the interceptor must begin a new * Jakarta Transactions transaction, the managed bean method execution must then continue * inside this transaction context, and the transaction must be completed by * the interceptor.

*

If called inside a transaction context, the current transaction context must * be suspended, a new Jakarta Transactions transaction will begin, the managed bean method * execution must then continue inside this transaction context, the transaction * must be completed, and the previously suspended transaction must be resumed.

*/ REQUIRES_NEW, /** *

If called outside a transaction context, a TransactionalException with a * nested TransactionRequiredException must be thrown.

*

If called inside a transaction context, managed bean method execution will * then continue under that context.

*/ MANDATORY, /** *

If called outside a transaction context, managed bean method execution * must then continue outside a transaction context.

*

If called inside a transaction context, the managed bean method execution * must then continue inside this transaction context.

*/ SUPPORTS, /** *

If called outside a transaction context, managed bean method execution * must then continue outside a transaction context.

*

If called inside a transaction context, the current transaction context must * be suspended, the managed bean method execution must then continue * outside a transaction context, and the previously suspended transaction * must be resumed by the interceptor that suspended it after the method * execution has completed.

*/ NOT_SUPPORTED, /** *

If called outside a transaction context, managed bean method execution * must then continue outside a transaction context.

*

If called inside a transaction context, a TransactionalException with * a nested InvalidTransactionException must be thrown.

*/ NEVER } /** * The rollbackOn element can be set to indicate exceptions that must cause * the interceptor to mark the transaction for rollback. Conversely, the dontRollbackOn * element can be set to indicate exceptions that must not cause the interceptor to mark * the transaction for rollback. When a class is specified for either of these elements, * the designated behavior applies to subclasses of that class as well. If both elements * are specified, dontRollbackOn takes precedence. * @return Class[] of Exceptions */ @Nonbinding public Class[] rollbackOn() default {}; /** * The dontRollbackOn element can be set to indicate exceptions that must not cause * the interceptor to mark the transaction for rollback. Conversely, the rollbackOn element * can be set to indicate exceptions that must cause the interceptor to mark the transaction * for rollback. When a class is specified for either of these elements, * the designated behavior applies to subclasses of that class as well. If both elements * are specified, dontRollbackOn takes precedence. * @return Class[] of Exceptions */ @Nonbinding public Class[] dontRollbackOn() default {}; }




© 2015 - 2024 Weber Informatics LLC | Privacy Policy