Hello, again,
problem was a stateful=false statement in the login form i missed.
setting it to true again did the trick.
Regards,
Patrick
Hello!
Our application is user based and therefore the first page shown is
the login page. As soon as the page is entered a new session for the
user is created. In Tapestry 4.1.1 this session was used for this user
as it should be. After switching to Tapestry 4.1.2 however, as soon as
the user hits the login button a new session is created additionally
which is used for the user.
So far this would only pose a small problem as the first session will
timeout sometime later.
The problem gets to a real nuisance as soon as the user should be
forced to change his password directly after logging in. When he
presses the change password button after entering the new password,
the next session is created to process the request and the user is
back on the initial login again without any data being stored (the
original password is still in place). Even if i put the password
change into another page the user is still not able to change his pw
as the visit object containing the user info is fresh as soon as this
page is loaded and the additional session kicks in.
All this worked well with T4.0.2 and T4.1.1
Does anyone have an idea of how to work around that dilemma?
Regards,
Patrick
---------------------------------------------------------------------
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]
