Hans Bergsten wrote:
> [...] > The spec may not be explicit enough about this, but the session object > you get back from the getSession() object is a container-managed object > that the application is not supposed/allowed to keep long-lived > references > to. It's the same as with all other container-objects made available to > the > application; request, response, JSP tag handlers, etc. > I'm not sure why you're keeping references to the session objects
in
> you're application, but if you describe what you're trying to do I'm > sure I can give you a hint about another way to accomplish the same > thing without the problems you have with your current solution. I am trying to disallow a single user to have multiple
login sessions valid at any given time. I have to enforce this even if the user
tried to login from two different machines.
Can you suggest a solution for this which works on tomcat 3.2.1 and uses
servlet specs 2.2 only.
Regds,
Gokul
|
- Re: NullPointerException... Christopher K. St. John
- Re: NullPointerException... Craig R. McClanahan
- Session passivation (was... Kief Morris
- Re: Session passivation ... Craig R. McClanahan
- Re: Session passivation ... Kief Morris
- Re: Session passivation ... Kief Morris
- one session for many web... Mihai Popoaei
- Re: one session for many... Craig R. McClanahan
- Re: one session for many... cmanolache
- Re: one session for many... Mihai Popoaei
- Re: NullPointerException from HttpSessionFacade.in... Gokul Singh
- Re: NullPointerException from HttpSessionFaca... Hans Bergsten
- Re: NullPointerException from HttpSession... Gokul Singh
- Re: NullPointerException from HttpSes... Hans Bergsten
- Re: NullPointerException from HttpSessionFaca... Craig R. McClanahan
- Re: NullPointerException from HttpSessionFacade.in... Gokul Singh
- Re: NullPointerException from HttpSessionFacade.in... Greg Brouelette