Nick Rumble wrote:
> This is a common misconception with COM+. COM+ is not inherently stateless.
> A COM+ object controls it's own lifetime by issueing a call to SetComplete()
> or SetAbort() when it's finished with its state. SetComplete() is not
> implicitely called at the end of each method call. Therefore COM+ objects
> can be either stateful or stateless. It is true that transaction semantics
> have to be defined at the coclass level (not method).
The term stateful is normally used to mean that state data is held outside the
scope of a transaction. SetComplete() is a vote to commit the transaction, and
SetAbort() is a vote to back the transaction out, so COM is essentially
stateless.
Microsoft's recommended way for COM obects to preserve state is to use the
(non-transactional) Stored Properties Manager (spelling?) APIs to save and load
state explicitly. A transactional version of the SPM was recently withdrawn when
they withdrew IMDB.
Ian McCallion
CICS Business Unit
IBM Hursley
[EMAIL PROTECTED]
Tel: ++44-1962-818065
Fax: ++44-1962-818069
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
