hello Christian -
As far as I know the session is managed by tomcat ( or any other
container ) - so maybe the tomcat list is a better place to ask...
but since it is managed by the container, I would suggest that relying
on a session id taken either from the url or from the cookie might cause
some problems if you change the container configuration.
If you want to implement long sessions or store some extra session
information outside of the session map itself (which seem to me two
reasons to try to capture the session id) I would suggest creating your
own id and, ofcause, store it in the session :)
Hope that helps,
Cheers,
Ron
Christian Mittendorf wrote:
Hello!
My Tapestry 4 based application uses the Home.page to read all url and
cookie parameters. The page then decides what to do next and it throws
a PageRedirectException in its pageBeginRender Method.
If I open this app in the browser, I'll first get a cookie with
JSESSIONID X. Then, on the page shown after the page redirect has taken
place, the app is using a different JSESSIONID in its rewritten urls
("/XYZ/app;jsessionid=Y").
In the end I turned off cookies for my app to make it work properly.
However, my question now is "why"? Why are the session ids from the
rewritten url and the cookie different? What am I missing?
Christian
---------------------------------------------------------------------
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]
