I was thinking of that too.. He did say in his initail post: "I'm keep on
calling this action for different
condition".. so the clue maybe hidden in that..
But then again, having been up since 3am, I perhaps shouldn't be posting
to any lists..;)
Geeta
Dave Newton <[EMAIL PROTECTED]> wrote on
[EMAIL PROTECTED] wrote:
You are quite right; I was being sloppy.. Should have added the "if
there's no current session" bit.. thanks for the catch..
Which makes me wonder why the original poster was continually getting
new sessions; seems weird.
Dave
Dave Newton <[EMAIL PROTECTED]> wrot
You are quite right; I was being sloppy.. Should have added the "if
there's no current session" bit.. thanks for the catch..
Geeta
Dave Newton <[EMAIL PROTECTED]> wrote on 08/16/2005 10:54:39 AM:
> [EMAIL PROTECTED] wrote:
>
> >HttpSession Session=request.getSession(true);
> >
> >The "true" mea
[EMAIL PROTECTED] wrote:
HttpSession Session=request.getSession(true);
The "true" means create a new session.
For which J2EE versions is that correct? In my 1.3 JavaDocs it says:
"Returns the current |HttpSession| associated with this request or, if
if there is no current session and |cre
Hi Senthilrajan:
As Hermod mentioned in his note, your session problems are caused because
you have (from your previous note):
HttpSession Session=request.getSession(true);
The "true" means create a new session. So instead use:
HttpSession Session=request.getSession(false);
or just:
HttpSession
5 matches
Mail list logo