You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Jeromy Evans (JIRA)" <ji...@apache.org> on 2008/11/27 00:49:37 UTC
[jira] Commented: (WW-2449) Support convention based action
chaining
[ https://issues.apache.org/struts/browse/WW-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45026#action_45026 ]
Jeromy Evans commented on WW-2449:
----------------------------------
Musachy asked me to do a review. 'll have a proper look, but I don't think I'd ever use this. What the main rationale or use-case?
In my apps, albeit mainly based on the rest plugin's paradigm, I've never encountered a need to chain. Default and unknown result handlers suit my circumstances. In cases where I have chained actions in the past I've ended up regretting the coupling later and having to remove it.
I expect there's no harm if its useful though.
> Support convention based action chaining
> ----------------------------------------
>
> Key: WW-2449
> URL: https://issues.apache.org/struts/browse/WW-2449
> Project: Struts 2
> Issue Type: New Feature
> Components: Plugin - Convention
> Affects Versions: 2.1.1
> Reporter: Brian Pontarelli
> Priority: Minor
> Fix For: 2.2.x
>
>
> Automatically chain actions together based on the return values and the current actions name and namespace. For example,
> package com.example.actions;
> public class FooAction {
> public String execute() {
> return "bar";
> }
> }
> This would look for the results foo-bar first and if they don't exist it would chain to an action named foo-bar.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.