Regarding stateful session bean chaining , why cant we have all beans
timeout together. The first stateful bean can create a timeout object and
this timeout object can be propagated to all subsequent stateful session
beans just like what Sun has done with transactions . That way we don't have
to worry about any intermediate bean timing out?Comments ..?
> -----Original Message-----
> From: david mcdonald [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, November 17, 1999 02:58
> To: [EMAIL PROTECTED]
> Subject: APM and stateful session beans
>
> In the Oreilly Enterprise Javabeans book, in the design strategies chapter
> ,
> it recommends not chaining stateful session beans. (p. 283)
> In the Sun APM (p.83) the Stateful session bean EStorekeeper calls the
> Shopping cart stateful session bean.
> Is this a good design strategy or not?
> Also the APM uses event driven state machines in the controller JSP and
> the
> controller Stateful session bean EStoreKeeper. Is this a good design
> strategy?
>
> dmcd
>
> ______________________________________________________
> Get Your Private, Free Email at http://www.hotmail.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".
