Hello Ralf,
sorry for not replying earlier. I have to check the list more frequently.
Ralf Fischer schrieb:
Hint: storing *everything* into the session might be unwise in some
circumstances, as all resources on a server are limited, even cheap memory.
everything == "everything that is necessary to make the login
interception transparent to the action" :-)
I would
use a simple redirect result as long as you have to deal with HTTP-GETs
only, as it's pretty hard to redirect a POST.
POST would be nice to have, but GET only will be fine ATM.
- Create a global result[1] which leads to the login page.
- When your interceptor thinks a login is required, store the requested
URL to the session and return the global login result from your
interceptor.
That's exactly what I'm already doing (except for storing the URL). Good
to get some approval!
- When the login action ends successfully, if an URL is in the session,
redirect to it using a simple redirect result with a parametrized url [2].
I will give it a try. Thank you for the hint.
Greetings,
~Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
