Dave
I think this document will explain why its better to use stateful session
beans than servlets holding state. Servlets can be used simply as a conduit
for bringing a client's invocation into the EJB container. All session state
management takes place in stateful session beans.
http://www.inprise.com/appserver/papers/11501_clustering.pdf
kind regards,
William Louth
> -----Original Message-----
> From: Dave Ford [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, April 18, 2000 12:16 PM
> To: [EMAIL PROTECTED]
> Subject: HttpSession versus EJB Session Bean
>
> When using ejbs with servlets (or jsp pages), do you typically store any
> client state in the HttpSession object or do you store all state in a
> session ejb? What I have been doing is merly storing remote references to
> ejbs in the HttpSession object, then storing all state in the ejb. Is that
> standard practice when using servlets with ejbs?
>
> Dave
>
> ==========================================================================
> =
> 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".
***********************************************************************
Bear Stearns is not responsible for any recommendation, solicitation,
offer or agreement or any information about any transaction, customer
account or account activity contained in this communication.
***********************************************************************
===========================================================================
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".
