[
https://issues.apache.org/struts/browse/WW-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Musachy Barroso resolved WW-1796.
---------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.1.x)
Future
Applied to Convention plugin in the sandbox. I also added "params" to
@IntereceptorRef, so an action can be configured like:
...
@Action(value="/test/hello", interceptorRefs = @InterceptorRef(value =
"roles", params = {"allowedRoles", "a,b"}))
public String execute() throws Exception {
setMessage(getText(MESSAGE));
return SUCCESS;
}
...
> @InterceptorRef and @InterceptorRefs annotations to configure actions with
> custom interceptor-refs
> --------------------------------------------------------------------------------------------------
>
> Key: WW-1796
> URL: https://issues.apache.org/struts/browse/WW-1796
> Project: Struts 2
> Issue Type: Improvement
> Components: Plugin - CodeBehind
> Reporter: Aadi Deshpande
> Fix For: Future
>
> Attachments: interceptor-ref.patch, interceptor-ref.patch
>
>
> This patch allows people to annotate their actions with @InterceptorRef and
> @InterceptorRefs to configure the interceptor stacks that the action is run
> with, bringing us one step closer to zero-conf.
> The ClasspathConfigurationProvider is where all the magic happens ( after
> ParentPackage configuration ).
> Notes:
> -Interceptors are stacked in the order they are listed, by whatever the
> InterceptorBuilder returns.
> -It is currently possible to have @InterceptorRef and @InterceptorRefs in
> the same action, but the @InterceptorRef will still be on top.
> -Most of my testing has been on the 2.0.x branch, but since there seem not to
> have been a lot of changes to the ClasspathConfigurationProvider ( if any )
> since that time, it's been a straightforward move.
> Patch is against trunk/core and includes the new annotation files as well
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
