Given that my stateful sessionbeans are already taking up a lot of memory, I want to keep my HTTPSession as light as possible.
It'll help to keep an ID rather than an object as a parameter. Any suggestions ? Cheers, Kunal -----Original Message----- From: Robert Taylor [mailto:[EMAIL PROTECTED] Sent: Friday, 28 May 2004 21:37 To: Struts Users Mailing List Subject: RE: [OT]: StatefulSessionBeans and HTTPSession Why? It appears that you already have the appropriate "best practices" solution. Are you trying to avoid using a BusinessDelegate? robert > -----Original Message----- > From: Kunal H. Parikh [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 27, 2004 9:15 PM > To: Struts Users Mailing List > Subject: [OT]: StatefulSessionBeans and HTTPSession > > > Hi All! > > Just wanted to know if there is a better strategy to do this. > > My current implementation: > Struts/JSP --> BusinessDelegate --> StatefulSessionBean --> Multiple > EntityBeans > > Now, I add the BusinessDelegate to my HttpSession, effectively keeping the > handle to my StatefulSessionBean. > > Instead, I was hoping, if it were possible, to store a StatefulSessionBeanID > in my HttpSession and recall the StatefulSessionBean using the ID from my > EJB tier. > > Let me know of your thoughts on this structure. > > > TIA, > > Kunal > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
