struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Thrasher (JIRA)" <>
Subject [jira] Updated: (WW-3426) ServletRedirectResult and ServletActionRedirectResult should support #anchor URI syntax
Date Thu, 01 Apr 2010 07:03:27 GMT


Jason Thrasher updated WW-3426:

    Attachment: WW-3426-core-RedirectResult.patch

The attached patch provides #anchor URI support for ServletRedirectResult and ServletActionRedirectResult.
 Unit tests are included as well.

Example usage in struts.xml action result:

<result name="success" type="redirectAction">
	<param name="namespace">/space</param>
	<param name="actionName">myAction</param>
	<param name="anchor">FRAGMENT</param>
	<param name="param1">${param1}</param>

> ServletRedirectResult and ServletActionRedirectResult should support #anchor URI syntax
> ---------------------------------------------------------------------------------------
>                 Key: WW-3426
>                 URL:
>             Project: Struts 2
>          Issue Type: Improvement
>          Components: Dispatch Filter
>    Affects Versions:
>            Reporter: Jason Thrasher
>         Attachments: WW-3426-core-RedirectResult.patch
>   Original Estimate: 1h
>  Remaining Estimate: 1h
> Expected URI syntax includes an "#anchor", as documented here:
>     "A fragment identifier component is indicated by the presence of a number sign ("#")
character and terminated by the end of the URI."
> ServletRedirectResult's current implementation allows anchor fragments to be used only
if there are no query parameters present for the RedirectResult.  In this case, the location
param can be specified for a ServletRedirectResult with a #anchor suffix.  However this does
not work when using query parameters.  ServletActionRedirectResult does not support #anchor
due to runtime discovery of the target URI based on the actionName, namespace, and method.
> Anchor fragments should be generally supported in redirection.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message