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

org.springframework.transaction.annotation.Transactional Maven / Gradle / Ivy

There is a newer version: 6.1.13
Show newest version
/*
 * Copyright 2002-2022 the original author or authors.
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *      https://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

package org.springframework.transaction.annotation;

import java.lang.annotation.Documented;
import java.lang.annotation.ElementType;
import java.lang.annotation.Inherited;
import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;
import java.lang.annotation.Target;

import org.springframework.core.annotation.AliasFor;
import org.springframework.transaction.TransactionDefinition;

/**
 * Describes a transaction attribute on an individual method or on a class.
 *
 * 

When this annotation is declared at the class level, it applies as a default * to all methods of the declaring class and its subclasses. Note that it does not * apply to ancestor classes up the class hierarchy; inherited methods need to be * locally redeclared in order to participate in a subclass-level annotation. For * details on method visibility constraints, consult the * Transaction Management * section of the reference manual. * *

This annotation is generally directly comparable to Spring's * {@link org.springframework.transaction.interceptor.RuleBasedTransactionAttribute} * class, and in fact {@link AnnotationTransactionAttributeSource} will directly * convert this annotation's attributes to properties in {@code RuleBasedTransactionAttribute}, * so that Spring's transaction support code does not have to know about annotations. * *

Attribute Semantics

* *

If no custom rollback rules are configured in this annotation, the transaction * will roll back on {@link RuntimeException} and {@link Error} but not on checked * exceptions. * *

Rollback rules determine if a transaction should be rolled back when a given * exception is thrown, and the rules are based on patterns. A pattern can be a * fully qualified class name or a substring of a fully qualified class name for * an exception type (which must be a subclass of {@code Throwable}), with no * wildcard support at present. For example, a value of * {@code "javax.servlet.ServletException"} or {@code "ServletException"} will * match {@code javax.servlet.ServletException} and its subclasses. * *

Rollback rules may be configured via {@link #rollbackFor}/{@link #noRollbackFor} * and {@link #rollbackForClassName}/{@link #noRollbackForClassName}, which allow * patterns to be specified as {@link Class} references or {@linkplain String * strings}, respectively. When an exception type is specified as a class reference * its fully qualified name will be used as the pattern. Consequently, * {@code @Transactional(rollbackFor = example.CustomException.class)} is equivalent * to {@code @Transactional(rollbackForClassName = "example.CustomException")}. * *

WARNING: You must carefully consider how specific the pattern * is and whether to include package information (which isn't mandatory). For example, * {@code "Exception"} will match nearly anything and will probably hide other * rules. {@code "java.lang.Exception"} would be correct if {@code "Exception"} * were meant to define a rule for all checked exceptions. With more unique * exception names such as {@code "BaseBusinessException"} there is likely no * need to use the fully qualified class name for the exception pattern. Furthermore, * rollback rules may result in unintentional matches for similarly named exceptions * and nested classes. This is due to the fact that a thrown exception is considered * to be a match for a given rollback rule if the name of thrown exception contains * the exception pattern configured for the rollback rule. For example, given a * rule configured to match on {@code com.example.CustomException}, that rule * would match against an exception named * {@code com.example.CustomExceptionV2} (an exception in the same package as * {@code CustomException} but with an additional suffix) or an exception named * {@code com.example.CustomException$AnotherException} * (an exception declared as a nested class in {@code CustomException}). * *

For specific information about the semantics of other attributes in this * annotation, consult the {@link org.springframework.transaction.TransactionDefinition} * and {@link org.springframework.transaction.interceptor.TransactionAttribute} javadocs. * *

Transaction Management

* *

This annotation commonly works with thread-bound transactions managed by a * {@link org.springframework.transaction.PlatformTransactionManager}, exposing a * transaction to all data access operations within the current execution thread. * Note: This does NOT propagate to newly started threads within the method. * *

Alternatively, this annotation may demarcate a reactive transaction managed * by a {@link org.springframework.transaction.ReactiveTransactionManager} which * uses the Reactor context instead of thread-local variables. As a consequence, * all participating data access operations need to execute within the same * Reactor context in the same reactive pipeline. * * @author Colin Sampaleanu * @author Juergen Hoeller * @author Sam Brannen * @author Mark Paluch * @since 1.2 * @see org.springframework.transaction.interceptor.TransactionAttribute * @see org.springframework.transaction.interceptor.DefaultTransactionAttribute * @see org.springframework.transaction.interceptor.RuleBasedTransactionAttribute */ @Target({ElementType.TYPE, ElementType.METHOD}) @Retention(RetentionPolicy.RUNTIME) @Inherited @Documented public @interface Transactional { /** * Alias for {@link #transactionManager}. * @see #transactionManager */ @AliasFor("transactionManager") String value() default ""; /** * A qualifier value for the specified transaction. *

May be used to determine the target transaction manager, matching the * qualifier value (or the bean name) of a specific * {@link org.springframework.transaction.TransactionManager TransactionManager} * bean definition. * @since 4.2 * @see #value * @see org.springframework.transaction.PlatformTransactionManager * @see org.springframework.transaction.ReactiveTransactionManager */ @AliasFor("value") String transactionManager() default ""; /** * Defines zero (0) or more transaction labels. *

Labels may be used to describe a transaction, and they can be evaluated * by individual transaction managers. Labels may serve a solely descriptive * purpose or map to pre-defined transaction manager-specific options. *

See the documentation of the actual transaction manager implementation * for details on how it evaluates transaction labels. * @since 5.3 * @see org.springframework.transaction.interceptor.DefaultTransactionAttribute#getLabels() */ String[] label() default {}; /** * The transaction propagation type. *

Defaults to {@link Propagation#REQUIRED}. * @see org.springframework.transaction.interceptor.TransactionAttribute#getPropagationBehavior() */ Propagation propagation() default Propagation.REQUIRED; /** * The transaction isolation level. *

Defaults to {@link Isolation#DEFAULT}. *

Exclusively designed for use with {@link Propagation#REQUIRED} or * {@link Propagation#REQUIRES_NEW} since it only applies to newly started * transactions. Consider switching the "validateExistingTransactions" flag to * "true" on your transaction manager if you'd like isolation level declarations * to get rejected when participating in an existing transaction with a different * isolation level. * @see org.springframework.transaction.interceptor.TransactionAttribute#getIsolationLevel() * @see org.springframework.transaction.support.AbstractPlatformTransactionManager#setValidateExistingTransaction */ Isolation isolation() default Isolation.DEFAULT; /** * The timeout for this transaction (in seconds). *

Defaults to the default timeout of the underlying transaction system. *

Exclusively designed for use with {@link Propagation#REQUIRED} or * {@link Propagation#REQUIRES_NEW} since it only applies to newly started * transactions. * @return the timeout in seconds * @see org.springframework.transaction.interceptor.TransactionAttribute#getTimeout() */ int timeout() default TransactionDefinition.TIMEOUT_DEFAULT; /** * The timeout for this transaction (in seconds). *

Defaults to the default timeout of the underlying transaction system. *

Exclusively designed for use with {@link Propagation#REQUIRED} or * {@link Propagation#REQUIRES_NEW} since it only applies to newly started * transactions. * @return the timeout in seconds as a String value, e.g. a placeholder * @since 5.3 * @see org.springframework.transaction.interceptor.TransactionAttribute#getTimeout() */ String timeoutString() default ""; /** * A boolean flag that can be set to {@code true} if the transaction is * effectively read-only, allowing for corresponding optimizations at runtime. *

Defaults to {@code false}. *

This just serves as a hint for the actual transaction subsystem; * it will not necessarily cause failure of write access attempts. * A transaction manager which cannot interpret the read-only hint will * not throw an exception when asked for a read-only transaction * but rather silently ignore the hint. * @see org.springframework.transaction.interceptor.TransactionAttribute#isReadOnly() * @see org.springframework.transaction.support.TransactionSynchronizationManager#isCurrentTransactionReadOnly() */ boolean readOnly() default false; /** * Defines zero (0) or more exception {@linkplain Class classes}, which must be * subclasses of {@link Throwable}, indicating which exception types must cause * a transaction rollback. *

By default, a transaction will be rolled back on {@link RuntimeException} * and {@link Error} but not on checked exceptions (business exceptions). See * {@link org.springframework.transaction.interceptor.DefaultTransactionAttribute#rollbackOn(Throwable)} * for a detailed explanation. *

This is the preferred way to construct a rollback rule (in contrast to * {@link #rollbackForClassName}), matching the exception type, its subclasses, * and its nested classes. See the {@linkplain Transactional class-level javadocs} * for further details on rollback rule semantics and warnings regarding possible * unintentional matches. * @see #rollbackForClassName * @see org.springframework.transaction.interceptor.RollbackRuleAttribute#RollbackRuleAttribute(Class) * @see org.springframework.transaction.interceptor.DefaultTransactionAttribute#rollbackOn(Throwable) */ Class[] rollbackFor() default {}; /** * Defines zero (0) or more exception name patterns (for exceptions which must be a * subclass of {@link Throwable}), indicating which exception types must cause * a transaction rollback. *

See the {@linkplain Transactional class-level javadocs} for further details * on rollback rule semantics, patterns, and warnings regarding possible * unintentional matches. * @see #rollbackFor * @see org.springframework.transaction.interceptor.RollbackRuleAttribute#RollbackRuleAttribute(String) * @see org.springframework.transaction.interceptor.DefaultTransactionAttribute#rollbackOn(Throwable) */ String[] rollbackForClassName() default {}; /** * Defines zero (0) or more exception {@link Class Classes}, which must be * subclasses of {@link Throwable}, indicating which exception types must * not cause a transaction rollback. *

This is the preferred way to construct a rollback rule (in contrast to * {@link #noRollbackForClassName}), matching the exception type, its subclasses, * and its nested classes. See the {@linkplain Transactional class-level javadocs} * for further details on rollback rule semantics and warnings regarding possible * unintentional matches. * @see #noRollbackForClassName * @see org.springframework.transaction.interceptor.NoRollbackRuleAttribute#NoRollbackRuleAttribute(Class) * @see org.springframework.transaction.interceptor.DefaultTransactionAttribute#rollbackOn(Throwable) */ Class[] noRollbackFor() default {}; /** * Defines zero (0) or more exception name patterns (for exceptions which must be a * subclass of {@link Throwable}) indicating which exception types must not * cause a transaction rollback. *

See the {@linkplain Transactional class-level javadocs} for further details * on rollback rule semantics, patterns, and warnings regarding possible * unintentional matches. * @see #noRollbackFor * @see org.springframework.transaction.interceptor.NoRollbackRuleAttribute#NoRollbackRuleAttribute(String) * @see org.springframework.transaction.interceptor.DefaultTransactionAttribute#rollbackOn(Throwable) */ String[] noRollbackForClassName() default {}; }





© 2015 - 2024 Weber Informatics LLC | Privacy Policy