Here is the what my situation looks like...
1) start container
2) log into app (flux loggin deal that comes with newapp)
3) logged in no prob... see valid jsessionid
4) javascript popup uses a $setPage link to open a new window.
5) this new window has a new jsessionid
(data.getCookies().get("jsessionid"))
6) log in on the new window
7) click link again
8) new window refreshes, as advertised
9) after that window closes, sometimes it wants me to login again.. I just
might need to mess with my timeout settings for this part...
10) old windows session never becomes invalid... that I can see...
so... how do I get the new window to have the same jsessionid as the parent?
do I need to pass it along in the link to the popup?
> If you're referring to a way to maintain client state on the server
> (i.e. user sessions), it's part of the Servlet API, and therefore
> built into your servlet container. Turbine's RunData interface is its
> main interaction with an HttpSession.
>
> If you're referring to generic cookie handling, take a look at
> CookieParser.
>
> ---------------------------------------------------------------------
> 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]
