* See the file LICENSE for redistribution information.
* Copyright (c) 2002, 2013 Oracle and/or its affiliates. All rights reserved.
TransactionTriggerdefines the methods that track a transaction through its lifecycle. The following table captures the relationship between transaction lifecycle operations and their trigger methods.
WARNING: Only transient triggers are currently supported, and the documention below has not yet been updated to reflect this fact. See details at the top of Trigger.java. Also see the warning at the top of ReplicatedDatabaseTrigger.java.
|Transaction Operation||Trigger Method|
The use of method names in the above table is intended to cover all overloaded methods with that name.
The trigger methods are also invoked for transactions that are implicitly initiated on behalf of the application in the following two cases:
A TransactionTrigger is associated with a database via
DatbaseTriggerdo not typically need to define Transaction triggers, since the changes they make are committed and rolled back automatically by this transaction. For example, triggers defined solely to create additional indexes in the environment do not need to define transaction triggers. Only sophisticated applications that manage state outside of JE, or in independent transactions typically define such triggers.
txnthe transaction that was committed
txnthe transaction that was aborted