The component and server properties and the component implementation determine how your CORBA component participates in transactions.
Defining how a component participates in transactions
Specify the component’s transaction attribute. Each component has a transaction attribute that determines whether instances of the component participate in transactions. “Transaction type values” describes the attribute settings and their meanings.
If long transactions are enabled in the server, and your CORBA component is stateful, code methods to call the EAServer transaction state primitives. Each method should call the appropriate transaction state primitive to reflect the state of the work that the component has contributed to the transaction. “Using transaction state primitives” describes the state primitives in detail.
If long transactions are disabled or the CORBA component is stateless, transactions end when each business method returns. Each business method can call completeWork or rollbackWork to influence the transaction outcome. If neither is called, the completeWork behavior is the default.
