I also used client-side session management for Traval Agent application (and Web-Container based session management for Customer application). But lots of other people here did otherwise. In my opinion, there is an scalability advantage into not tying session management to the EJB tier, but you should weight this in contrast with the code/setup reuse and other advantages that a backend-managed session can offer.
Decisions, decisions, decisions... that's all Part II is about!
I too buy that.The idea to keep SESSION as an Sateful EJB is when the seesion needs to be mainted close to the business layer.but as you said this approach is very suitable for the requirement. Since we can re-use the Stateful SESSION BEAN both for application and webclient.I am also going to follow this approach.Please suggest me if i am wrong.
Joined: Jun 16, 2005
I don't think you are "wrong", but I think one of the requirements of the assignment is to make the application client as snappy as possible, while stateful session EJBs are known to be a performance bottleneck.