Yes, but this would mean changing all beans to stateful instead of stateless, when it is only a single piece of information per client that differs.
I realise stateful beans would solve the problem, but I don't like the extra overhead, and prefer to stick with stateless beans if at all possible since the components are more lightweight and robust. Instead of making all beans stateful would like just one stateful bean - but to access this from stateless bean (if possible) presumably need to pass it an Id/handle? Joe. ----- Original Message ----- From: Kevin Gaasch <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, October 16, 2002 12:28 PM Subject: Re: maintaining state > But, like you said, it doesn't make any sense for keeping client state > from the stateless beans caller. You really need to use a statefull > bean. Your doing way to much work trying to figure out how to maintain > state when the stateful bean does it for you. > > Kevin E. Gaasch > Panhandle Plains Student Loan Center > Software Craftsman > Work: 806.324.4100 x4215 > Cell: 806.674.1523 > > =========================================================================== > 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".
