Gracefully continuing an interrupted action flow

["Mitchell, Steven" <St...@umb.com>]

Is there a best practice for capturing a user's original destination
when interrupting a request with an interceptor with the intention of
allowing them to continue on their way later... like form authentication
does? In my case I have a "Cookie Enforcer Interceptor" that checks for
the presence of a preference cookie.  It sends the user to the
preference page if the cookie is missing, but should then send them back
to where they were trying to go once the preference value has been set.

My plan is to put a global forward name in the session that corresponds
to a global forward which redirects to some action (there are several
possible destinations). I can then add another interceptor that looks
for that session attribute, returning (and removing) the forward name if
present. That sounds workable, but not very elegant.  

Steve Mitchell
Byteworks, Inc. <http://www.ByteworksInc.com> 
	



------------------------------------------------------------------------------
NOTICE:  This electronic mail message and any attached files are confidential.  The information is exclusively for the use of the individual or entity intended as the recipient.  If you are not the intended recipient, any use, copying, printing, reviewing, retention, disclosure, distribution or forwarding of the message or any attached file is not authorized and is strictly prohibited.  If you have received this electronic mail message in error, please advise the sender by reply electronic mail immediately and permanently delete the original transmission, any attachments and any copies of this message from your computer system. Thank you.

==============================================================================


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org

Re: Gracefully continuing an interrupted action flow

[Paweł Wielgus <po...@gmail.com>]

Hi Steve,
in my last app i have implemented it with interceptor that catches not
logged user, saves all necessary data to return to original request
into session and forwards to a login-input.jsp then in LoginAction i
check if there is such data in session and if there is i redirect to
the users primary target. Just don't forget to save parameters along
with uri.

Best greetings,
Pawel Wielgus.

2009/6/19, Mitchell, Steven <St...@umb.com>:
> Is there a best practice for capturing a user's original destination
> when interrupting a request with an interceptor with the intention of
> allowing them to continue on their way later... like form authentication
> does? In my case I have a "Cookie Enforcer Interceptor" that checks for
> the presence of a preference cookie.  It sends the user to the
> preference page if the cookie is missing, but should then send them back
> to where they were trying to go once the preference value has been set.
>
> My plan is to put a global forward name in the session that corresponds
> to a global forward which redirects to some action (there are several
> possible destinations). I can then add another interceptor that looks
> for that session attribute, returning (and removing) the forward name if
> present. That sounds workable, but not very elegant.
>
> Steve Mitchell
> Byteworks, Inc. <http://www.ByteworksInc.com>
> 	
>
>
>
> ------------------------------------------------------------------------------
> NOTICE:  This electronic mail message and any attached files are
> confidential.  The information is exclusively for the use of the individual
> or entity intended as the recipient.  If you are not the intended recipient,
> any use, copying, printing, reviewing, retention, disclosure, distribution
> or forwarding of the message or any attached file is not authorized and is
> strictly prohibited.  If you have received this electronic mail message in
> error, please advise the sender by reply electronic mail immediately and
> permanently delete the original transmission, any attachments and any copies
> of this message from your computer system. Thank you.
>
> ==============================================================================
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org