I disagree, "chaining" session beans is a problem only if they are stateful.
Stateless components can be nested without such concerns.
-Chris.
> -----Original Message-----
> From: Murali Krishna Devarakonda [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, January 05, 2000 9:15 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Multiple Session Beans in a Transaction
>
> ----- Original Message -----
> From: "Roger M" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, January 05, 2000 5:09 PM
> Subject: Multiple Session Beans in a Transaction
>
>
> > Is it possible to have a transaction spanning multiple
> > session bean objects ? Assuming all the session beans
> > are stateful
>
> It's a really bad idea to chain stateful session beans.
> See Monson-Haefel's book (Oreilly press) for a detailed explanation, but
> the
> issue is timeouts.
>
> > and implement SessionSynch interface,
>
> > what happens when the transaction rollsback ?
>
> It depends on the transaction context- such as MANDATORY or REQUIRES_NEW
> of
> each of the EJBs. Once you're clear about that, the answer would be
> self-evident.
>
> Regards,
> Murali Krishna Devarakonda
> e: [EMAIL PROTECTED]
>
> [...snip...]
>
> ==========================================================================
> =
> 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".
