Rickard �berg wrote:
> Hi!
>
> Consider the following:
> If I have a stateful sessionbean which is marked with TX_REQUIRES_NEW,
> and a method is invoked which updates some variables in the bean, but
> before it can return the tx is for some reason rolled back. What will
> happen with the state of the bean?
>
A comparison can be drawn between transactional stateful session beans and a
CORBA Transactional Server object. For the conversational state of the bean to
behave in a transactional manner the session bean's behaviour would need to be
modelled on the behaviour of a CORBA Recoverable Server object. A Transactional
Server object need not neccesarily be a Recoverable Server. For a full
explanation, refer to the CORBA Services spec section for Transactions, which
provides a good description of the distinction between the two types of
server.
>
> Since it is transactional one would imagine that the state would be
> restored to what it was before the method was invoked. However, this
> would require that the bean was stored (i.e. serialized) prior to the
> invocation. Is this the intent of the spec. (Vlada?), and are any
> vendors implementing it this way? Is the
> SessionSynchronization-interface supposed to cover this?
Yes, it can do. Tom covers this in his reply.
>
>
> Thanks,
> Rickard
>
> --
> Rickard �berg
>
> Computer Science student@LiTH
> @home: +46 13 177937
> Email: [EMAIL PROTECTED]
> Homepage: http://www-und.ida.liu.se/~ricob684
>
> ===========================================================================
> 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".
===========================================================================
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".
