This is why the EJB spec contains a session synchronization interface.
Your session bean can implement the callbacks defined in this
interface to roll back your session state when needed.
Regards,
Frank Sauer
The Technical Resource Connection
a wholly owned subsidiary of Perot Systems
Tampa, FL
http://www.trcinc.com
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Kenneth D. Litwak
> Sent: Wednesday, July 05, 2000 5:44 PM
> To: [EMAIL PROTECTED]
> Subject: Transaction commit/rolback for stateful session beans
>
>
> In the following scenario
> caller calls a method of a stateful session bean
> the bean's method uses CMT
> The transaction attribute is REQUIRES or REQUIRES_NEW
>
> the method call modifies the state of the stateful session
> bean. Something,
> however, happens that causes he container to rollback the
> transaction. Since,
> so far as I know, containers don't do anything to keep track
> of state in a
> stateful session bean, they have no way to rolllback the
> changes to the session
> bean. Doesn't this then make TXs for session bean, unless
> they are only
> modifying entity beans, irrelevant at best, and a waste of
> resources at worst,
> because youare wasting time to start and stop a transaction
> that has no effect
> on the bean invovled? Thanks.
>
>
> Ken
>
> ==============================================================
> =============
> 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".
