> Hey Thanks very much Dmitri so in reference to my architecture I explained > before, you are saying :
of course Juan put in the vital piece of information that I left out, being that if you want your HttpSessions to be serializable you'll need to store the handle, not the stub. > 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? are you thinking something like this: web tier -> slsb -> sfsb -> eb ? because that wont work, unless you passed the handle to the sfsb to the slsb or something weird like that. I've never had a need for sfsb, so perhaps my advice is off, but if I were you I would just make the CustomerServer ejb a SFSB. This should mean you dont have to change much code at all. hth 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".
