Merge pull request #22809 from johnlinp
* pr/22809: Polish "Remove PROPAGATION_ prefix in Javadoc" Remove PROPAGATION_ prefix in Javadoc
This commit is contained in:
commit
fa848805fb
|
|
@ -1,5 +1,5 @@
|
|||
/*
|
||||
* Copyright 2002-2018 the original author or authors.
|
||||
* Copyright 2002-2019 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.
|
||||
|
|
@ -40,7 +40,7 @@ public enum Propagation {
|
|||
* Support a current transaction, execute non-transactionally if none exists.
|
||||
* Analogous to EJB transaction attribute of the same name.
|
||||
* <p>Note: For transaction managers with transaction synchronization,
|
||||
* PROPAGATION_SUPPORTS is slightly different from no transaction at all,
|
||||
* {@code SUPPORTS} is slightly different from no transaction at all,
|
||||
* as it defines a transaction scope that synchronization will apply for.
|
||||
* As a consequence, the same resources (JDBC Connection, Hibernate Session, etc)
|
||||
* will be shared for the entire specified scope. Note that this depends on
|
||||
|
|
@ -87,7 +87,7 @@ public enum Propagation {
|
|||
|
||||
/**
|
||||
* Execute within a nested transaction if a current transaction exists,
|
||||
* behave like PROPAGATION_REQUIRED else. There is no analogous feature in EJB.
|
||||
* behave like {@code REQUIRED} else. There is no analogous feature in EJB.
|
||||
* <p>Note: Actual creation of a nested transaction will only work on specific
|
||||
* transaction managers. Out of the box, this only applies to the JDBC
|
||||
* DataSourceTransactionManager when working on a JDBC 3.0 driver.
|
||||
|
|
|
|||
Loading…
Reference in New Issue