SFSB and HttpSession

[Sainudheen Mydeen]

Hi All
SFSB maintain state between method invocations. Like wise HttpSeeeion can also maintain the state. Then why do we need to step in to the complexity of Stateful SessionBean (interfaces, bean class etc..). I misunderstood the concept?
Thanks
-Sainudheen

[Basu DN]

Originally posted by Sainudheen Mydeen:
Hi All
SFSB maintain state between method invocations. Like wise HttpSeeeion can also maintain the state. Then why do we need to step in to the complexity of Stateful SessionBean (interfaces, bean class etc..). I misunderstood the concept?
Thanks
-Sainudheen

[Basu DN]

Originally posted by Sainudheen Mydeen:
Hi All
SFSB maintain state between method invocations. Like wise HttpSeeeion can also maintain the state. Then why do we need to step in to the complexity of Stateful SessionBean (interfaces, bean class etc..). I misunderstood the concept?
Thanks
-Sainudheen

Sorry for empty previous message..
SFSB is useful if we've multiple clients like J2ME client,Swing client,EJB client,Web Client wants to participate in the session related operations. If we use HttpSession then web client is only used ...

[Brian Nice]

Using SFSB also lets you participate in transactions provided by the container. Using the Http Session you would have to implement that yourself.
Also, the HttpSession is only available is you have an HttpServletRequest class around. So it is not useful for applications that do not have access to this.
Brian

[Sivasundaram Umapathy]

Folks,lets hear what sun recommends for maintaining client state
http://java.sun.com/blueprints/qanda/app_arch/index.html