Re: Why store session in Session Bean instead of HttpSession?

[Fei Li]

Title: Why store session in Session Bean instead of HttpSession?

Seems to me Stateful session bean is not necessary. Strore a bean in a HttpSession = Stateful session bean, right? If you want to use Stateful session bean you still need to create it in a HTTPSession object (maybe a bean), right? So, why Sateful session bean? Why J2EE specification does not make it direct? I mean, just like Session,getSession(), there should be a function called Session.getSessionBean("beanLookupName"). Is that not good?   Fei Li       ----- Original Message ----- From: Dennis Xi To: [EMAIL PROTECTED] Sent: Thursday, October 10, 2002 2:42 PM Subject: Re: Why store session in Session Bean instead of HttpSession? One stateful session bean for one client. To HttpSession, it's applicability of EJB. If HttpSession is enough, stateful session isn't necessary. --__--__--     ----- Original Message ----- From: Fei Li To: [EMAIL PROTECTED] Sent: Thursday, October 10, 2002 9:24 AM Subject: Re: Why store session in Session Bean instead of HttpSession? Hi List,   Question: If I create a Stateful Session Bean from a Servlet, When client A and B use the Servlet, the container creates 2 Stateful Session Beans for each client or creates only one Stateful Sesion Beans for both?   Thanks   Fei Li ----- Original Message ----- From: Cengiz KAYAY To: [EMAIL PROTECTED] Sent: Wednesday, October 09, 2002 10:59 PM Subject: Why store session in Session Bean instead of HttpSession? Hello List; I wonder why someone would need to use STSB and undergo a resource usage problem instead of just  using the HttpSession. Is the idea to use your own session object rather than storing objects under keys in the hashtable? Regards Cengiz Kayay