Hey Thanks very much Dmitri so in reference to my architecture I explained before, you are saying :
1. that SFSB does not have to be hidden behind my CustomerService? 2. I have not used SFSB at all thus I am not sure of their use. However, I was under impression that the commands from the client should be serviced behind a facade like the Customer Serivce (SLSB) and related beans should hidden behind it (including SFSB)? Is this senarion an exception? Glenn ----- Original Message ----- From: "Dmitri Colebatch" <[EMAIL PROTECTED]> To: "GlennODickson" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, September 12, 2002 12:45 PM Subject: Re: Stateful Session Beans > > 1. Where would be an appropriate in this structure to place a bean that > holds the customers login details and session state ? Would > > you create another bean called CustomerSession (SFSB) or make the Customer > Service a SFSB? > > I would store the data in the web tier under the HttpSession and pass it to > the ejb tier as required. although using a sfsb would achieve the same > results. > > > 2. How would this SFSB be referenced ? I don't understand how the SFSB can > be retrieve at some time later to use the session > > details. > > store the stub in the HttpSession. > > cheers > dim > > > > =========================================================================== 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".
