Indicate that the component’s work for the current transaction has been successfully completed and is ready to be committed.
void JagCompleteWork();
JagCompleteWork specifies that the component has successfully completed its contribution to the current transaction. The component instance deactivates when control returns from the current component method invocation.
If the component instance is the initiator of the transaction (that is, it was instantiated directly by a base client), then the component dispatcher attempts to commit the transaction. The transaction commits unless the commit is disallowed or vetoed; depending on the components that are participating, this can happen in any of the following ways:
A participating C or C++ component has called JagDisallowCommit.
A participating Java component throws an exception from its ServerBean.deactivate() method.
A participating ActiveX component has called IObjectContext::disableCommit().
If a component is not transactional, then JagCompletework and JagRollbackWork have the same effect: both cause the component instance to deactivate after the currently executing method returns.
If a method calls none of JagCompleteWork, JagContinueWork, JagDisallowCommit, or JagRollbackWork, the default behavior is that of JagContinueWork.
JagContinueWork, JagDisallowCommit, JagRollbackWork
Chapter 2, “Understanding Transactions and Component Lifecycles,” in the EAServer Programmer’s Guide
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
