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

[Marco Wang]

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

It depends how you implement your servlet.   Cheers, Marco ---------------------------- Marco Wang Meriton Networks 3026 Solandt Road Ottawa ON, K2K 2E1 Phone: (613)270-9279 Ext. 250 Fax:   (613)270-9628 [EMAIL PROTECTED] -----Original Message----- From: Jos� P�rez [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 10, 2002 12:31 PM To: [EMAIL PROTECTED] Subject: Re: Why store session in Session Bean instead of HttpSession? The container creates 2 stateful session beans      ----Mensaje original----- De: A mailing list for Enterprise JavaBeans development [mailto:[EMAIL PROTECTED]]En nombre de Fei Li Enviado el: jueves, 10 de octubre de 2002 18:25 Para: [EMAIL PROTECTED] Asunto: 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