Package javax.transaction
Interface Status
public interface Status
The Status interface defines static variables used for transaction
status codes.
-
Field Summary
Modifier and TypeFieldDescriptionstatic final int
A transaction is associated with the target object and it is in the active state.static final int
A transaction is associated with the target object and it has been committed.static final int
A transaction is associated with the target object and it is in the process of committing.static final int
A transaction is associated with the target object and it has been marked for rollback, perhaps as a result of a setRollbackOnly operation.static final int
No transaction is currently associated with the target object.static final int
A transaction is associated with the target object and it has been prepared.static final int
A transaction is associated with the target object and it is in the process of preparing.static final int
A transaction is associated with the target object and the outcome has been determined to be rollback.static final int
A transaction is associated with the target object and it is in the process of rolling back.static final int
A transaction is associated with the target object but its current status cannot be determined.
-
Field Details
-
STATUS_ACTIVE
static final int STATUS_ACTIVEA transaction is associated with the target object and it is in the active state. An implementation returns this status after a transaction has been started and prior to a Coordinator issuing any prepares, unless the transaction has been marked for rollback.- See Also:
-
STATUS_MARKED_ROLLBACK
static final int STATUS_MARKED_ROLLBACKA transaction is associated with the target object and it has been marked for rollback, perhaps as a result of a setRollbackOnly operation.- See Also:
-
STATUS_PREPARED
static final int STATUS_PREPAREDA transaction is associated with the target object and it has been prepared. That is, all subordinates have agreed to commit. The target object may be waiting for instructions from a superior as to how to proceed.- See Also:
-
STATUS_COMMITTED
static final int STATUS_COMMITTEDA transaction is associated with the target object and it has been committed. It is likely that heuristics exist; otherwise, the transaction would have been destroyed and NoTransaction returned.- See Also:
-
STATUS_ROLLEDBACK
static final int STATUS_ROLLEDBACKA transaction is associated with the target object and the outcome has been determined to be rollback. It is likely that heuristics exist; otherwise, the transaction would have been destroyed and NoTransaction returned.- See Also:
-
STATUS_UNKNOWN
static final int STATUS_UNKNOWNA transaction is associated with the target object but its current status cannot be determined. This is a transient condition and a subsequent invocation will ultimately return a different status.- See Also:
-
STATUS_NO_TRANSACTION
static final int STATUS_NO_TRANSACTIONNo transaction is currently associated with the target object. This will occur after a transaction has completed.- See Also:
-
STATUS_PREPARING
static final int STATUS_PREPARINGA transaction is associated with the target object and it is in the process of preparing. An implementation returns this status if it has started preparing, but has not yet completed the process. The likely reason for this is that the implementation is probably waiting for responses to prepare from one or more Resources.- See Also:
-
STATUS_COMMITTING
static final int STATUS_COMMITTINGA transaction is associated with the target object and it is in the process of committing. An implementation returns this status if it has decided to commit but has not yet completed the committing process. This occurs because the implementation is probably waiting for responses from one or more Resources.- See Also:
-
STATUS_ROLLING_BACK
static final int STATUS_ROLLING_BACKA transaction is associated with the target object and it is in the process of rolling back. An implementation returns this status if it has decided to rollback but has not yet completed the process. The implementation is probably waiting for responses from one or more Resources.- See Also:
-