Ken, SFSB should not be used as a server-side cache. If that's the design intent, it's a slippery slope.
Entity beans behind a SLSB (like I mentioned yesterday) would be a more prudent design. One bean (type) gets exposed to all clients (wireless, web, whatever) and data gets cached on the server side via entity beans. cheers, peter -----Original Message----- From: A mailing list for Enterprise JavaBeans development [mailto:[EMAIL PROTECTED]]On Behalf Of Kenneth D. Litwak Sent: Wednesday, October 24, 2001 9:33 AM To: [EMAIL PROTECTED] Subject: Sharing stateful session beans I'm trying to figure out a way to have a stateful session bean which is used by both a normal web client and the later, possibly, a wireless client. I would likeit to be the same sessin bean, but so far as I know, even if I had a handle to the bean, this is illegal because you can't have two callers for the same bean. What can I do for this? Also, if two users can't share a session bean, what's the point of a hdndle to the EJBObject? Thanks. Ken =========================================================================== 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".
