Early deactivation prevents a client application from tying up the resources (such as connections) that are associated with a component instance.
To support early deactivation in CORBA and PowerBuilder components you can use one of these methods:
Use a stateless component, which deactivates the component instance after each method invocation—see “Stateful versus stateless components”.
In a stateful component, configure the number of seconds an active component instance can remain idle before the client’s proxy becomes invalid—see “Passivation Timeout” in Table 4-2.
Code your component to call one of the completeWork or rollbackWork transaction state primitives to cause explicit deactivation of the instance. This technique is useful when your design requires deactivation to occur after some, but not all, method invocations. If the component is transactional, the completeWork and rollbackWork primitives also affect the outcome of the transaction in which the component is participating. See “Using transaction state primitives” for more information.
