Originally posted by Joe Nguyen:
By keeping in the httpSession, you're tempting to use stateless session bean in place of stateful session bean; this practice increases overhead and have been considered to be bad practice (google).
It depends on where state's belong to. If it's belong to HttpSession, then it 's better be in the HttpSession. Otherwise, it's be in the stateful sb
Hi Joe,
why does it increase overhead? On the contrary, it should decrease overhead
since I soley use leightweight SLSB and no expensive SFSB. On the other hand, I will have to pass more data as parameters over the wires since I have to always post all the state information to the SLSB.
The client state belongs to the client, so technically it should be kept in the HttpSession, but on the other hand business logic has to work with client information so EJBs work with the client state, so one may say it belongs to a SFSB...
Can you post your resource where saying that keeping client state in HttpSession and using SLSB is concidered bad practice?
D.