From de2e201a2abd9b9ba945e3bd231f78327dc0b1f7 Mon Sep 17 00:00:00 2001 From: Sam Brannen Date: Thu, 10 Sep 2015 19:35:17 +0200 Subject: [PATCH] Refer to @Commit instead of @Rollback(false) in the reference manual --- src/asciidoc/testing.adoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/asciidoc/testing.adoc b/src/asciidoc/testing.adoc index 3386c9d690..12995d93fd 100644 --- a/src/asciidoc/testing.adoc +++ b/src/asciidoc/testing.adoc @@ -264,7 +264,7 @@ application context. If you want a transaction to commit -- unusual, but occasionally useful when you want a particular test to populate or modify the database -- the TestContext framework can be instructed to cause the transaction to commit instead of roll back via the -<> annotation. +<> annotation. See transaction management with the <>. @@ -3142,7 +3142,7 @@ See <> for an additional example. By default, test transactions will be automatically rolled back after completion of the test; however, transactional commit and rollback behavior can be configured declaratively -via the `@Rollback` annotation. See the corresponding entry in the +via the `@Commit` and `@Rollback` annotations. See the corresponding entries in the <> section for further details. [[testcontext-tx-programmatic-tx-mgt]] @@ -3239,7 +3239,7 @@ declarative SQL script execution with default transaction rollback semantics. @RunWith(SpringJUnit4ClassRunner.class) @ContextConfiguration @Transactional(transactionManager = "txMgr") - **@Rollback(false)** + **@Commit** public class FictitiousTransactionalTest { **@BeforeTransaction** @@ -3254,7 +3254,7 @@ declarative SQL script execution with default transaction rollback semantics. @Test // overrides the class-level default rollback setting - **@Rollback(true)** + **@Rollback** public void modifyDatabaseWithinTransaction() { // logic which uses the test data and modifies database state }