It would be much cleaner to make the transaction client demarcated, but that
is generally not recommended for scalability/performance reasons.
-Chris.
> -----Original Message-----
> From: Madhusudan Iyengar [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, October 01, 1999 11:51 AM
> To: [EMAIL PROTECTED]
> Subject: Cancel a process
>
> Hi all
>
> I have a few SQL statements which need to be executed on the server. I
> have
> put them all in one method and one transaction because I want all or none
> to
> execute. I also need the client to be able to cancel the whole
> transaction
> if he wants to.
>
> I have a stateful session bean with two methods first method which does
> all
> the updates and deletes. The second one just raises a flag. The first one
> keeps checking for the flag before executing the next sql statement. If
> the
> flag is set to false i throw an exception and get out of the method so
> everything gets rolled back. My isolation level is
> TRANSACTION_SERIALIZABLE.
>
> Any suggestions as to how this can be implemented with the different
> transaction attributes that is available or
> Is my only option bean managed?
>
> Any suggestions would be appreciated.
>
> Madhu
>
>
>
>
>
>
>
>
> ________________________________________________________________
> Get FREE voicemail, fax and email at http://voicemail.excite.com
> Talk online at http://voicechat.excite.com
>
> ==========================================================================
> =
> 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".
