what I meant was that I am using stateless beans but need to maintain some stateful information for each client - which can be accessed somehow by the stateless beans.
As far as I know a stateless bean cannot call a stateful bean (which doesn't make sense anyhow) - so was wondering if there is a pattern to get around this problem. cheers, Joe. ----- Original Message ----- From: Dimitar Stavrakov <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 15, 2002 7:42 PM Subject: Re: maintaining state > Hi Joe, > > Usually you would want to pass client specific information to the stateless > session bean, not the other way around. That's why its called stateless - > doesn't keep state. > > Regards, > > Dimitar > > -----Original Message----- > From: Joe Ryan [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, October 15, 2002 12:53 PM > To: [EMAIL PROTECTED] > Subject: maintaining state > > Hi All, > > I am wondering if anyone knows a way of accessing client specific > information from a stateless bean; i.e; client info would be contained in a > stateful bean. > All our beans are stateless so seems like I need a pattern for maintaining > state. > > Thanks > Joe > > =========================================================================== > 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". =========================================================================== 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".
