It might help to know the structure by which you control login and
navigation inside the authorized portion of your application.
In my case, all the login forms explicitly return the Overview page :
public onSuccessFromForm(){
// Login validation
return overview;
}
@InjectPage
private Overview overview;
Is there some structure to your application that prevents this from
being a usable pattern?
On 06/14/2011 04:07 PM, sunilmanu wrote:
Hello Everyone,
After the user is kicked out of a session and they try to login back,
Tapestry tries to take the user back to the last requested Page or tries to
execute the last requested Action ? Why does it behave like that ?
Is there a way I can configure it to go to a "PAGE-123" always after the
user logs in successfully ALL the time ? Right now because of this issue,
lot of users are complaining and they are getting Stale Link Exception
because after logging in it tries to take them to a page and lot of
information might be missing and it breaks.
So plzzzz help or point me to right direction... !! Is there any particular
Cookie I need to delete when the redirect happens ?
thanks in advance for all the help...
thanks,
Sunil
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Tapestry-Remembers-which-page-to-navigate-after-User-Logs-in-tp4489125p4489125.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
