Plzzz help problem with session invalidate method ...

2004-02-03 Thread Vinay Kumar Munikuntla
Hi

I don;t know if this is the right place to ask this quesion .. ?

After  I invalidate a session using request.getSession().invalidate() I
forward the Login screen to the user.
When the user logs into the application I see that he has the same Session
Id as before the session was invalidated.

But this does not happen if the Browser window is closed and the new browser
window is opened.

How can I get a new session id each time the user logs in?

Vinay Kumar Munikuntla
[EMAIL PROTECTED]


-
This email, including any attachments, is for the designated recipient(s) only and may 
contain confidential, proprietary, and/or legally privileged information.  If you are 
not a designated recipient, or have received it in error, please notify the sender and 
destroy it and all attachments and copies immediately, without distributing, 
disclosing, or using it in any manner.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Plzzz help problem with session invalidate method ...

2004-02-03 Thread Gopalakrishnan, Jayesh
Check the HttpServletRequest API, there's a 
getSession(boolean) method that'll get u a new session 
Or an existing session based on true or false parameter. 

Make sure you use the right one in the login process.


hth
-jayash

-Original Message-
From: Vinay Kumar Munikuntla [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 03, 2004 8:59 AM
To: [EMAIL PROTECTED]
Subject: Plzzz help problem with session invalidate method ...


Hi

I don;t know if this is the right place to ask this quesion .. ?

After  I invalidate a session using request.getSession().invalidate() I
forward the Login screen to the user.
When the user logs into the application I see that he has the same Session
Id as before the session was invalidated.

But this does not happen if the Browser window is closed and the new browser
window is opened.

How can I get a new session id each time the user logs in?

Vinay Kumar Munikuntla
[EMAIL PROTECTED]


-
This email, including any attachments, is for the designated recipient(s)
only and may contain confidential, proprietary, and/or legally privileged
information.  If you are not a designated recipient, or have received it in
error, please notify the sender and destroy it and all attachments and
copies immediately, without distributing, disclosing, or using it in any
manner.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Session invalidate()

2001-04-24 Thread Darryl

Hi all,

Quick question about session.invalidate(). I created a login management
framework that works fine but for one problem. When I introduce the
session.invalidate() command for when the user logs out, naturally, all
the Struts-required beans in the session are destroyed so a
mapping.findforward(success) will also, naturally, fail.

Given these obvious consequences, surely someone out there has dealt
with this before. How does one invalidate a session without hozing all
your Struts objects placed in the session... or better put, how does
Struts implement session invalidation.

thanks,
Darryl

P.S. I did search the archived messages that I have but couldn't find
anything dealing with this topic.




Re: Session invalidate()

2001-04-24 Thread Darryl

Sorry all. Please ignore my previous post. My assumptions were completely
wrong. You can use invalidate() since mapping variables are in application
scope, and in fact I had already put an invalidate() in my code which was
why the second invalidate() I added was throwing an exception.  Sorry
about the brainfart.

- Darryl

Darryl wrote:

 Hi all,

 Quick question about session.invalidate(). I created a login management
 framework that works fine but for one problem. When I introduce the
 session.invalidate() command for when the user logs out, naturally, all
 the Struts-required beans in the session are destroyed so a
 mapping.findforward(success) will also, naturally, fail.

 Given these obvious consequences, surely someone out there has dealt
 with this before. How does one invalidate a session without hozing all
 your Struts objects placed in the session... or better put, how does
 Struts implement session invalidation.

 thanks,
 Darryl

 P.S. I did search the archived messages that I have but couldn't find
 anything dealing with this topic.