[
https://issues.apache.org/struts/browse/WW-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
spiker updated WW-2991:
-----------------------
Attachment: diff_to_2_1_6.txt
ConventionUnknownHandler.java
This is my work on this issue except the full-action-name-based result.
And I found xwork did not cache returned results and actions. I need to
implement some unknown-result cache and unknown-action cache to improve
performance.
> More intelligent result mapping.
> --------------------------------
>
> Key: WW-2991
> URL: https://issues.apache.org/struts/browse/WW-2991
> Project: Struts 2
> Issue Type: New Feature
> Components: Plugin - Convention
> Affects Versions: 2.1.6
> Reporter: spiker
> Attachments: ConventionUnknownHandler.java, diff_to_2_1_6.txt
>
>
> More intelligent result mapping could make Convention plugin more
> conventional. Here was my some initial thought:
> In my personal experience, most of the time, logical result name was not
> necessary.
> If the result string was "create.jsp", it will be dispatch to "create.jsp"
> under same package in "/WEB-INF/content". No need to look up "create.vm" or
> other guess work, performance will also increase.
> If the result string was "/login.jsp", it will be dispatch to
> "/WEB-INF/content/login.jsp" .
> If the result string was "redirect:create.jsp", then change result type to
> "redirect".
> If the result string was "edit.action", it will be chained to "EditAction"
> under same namespace.
> If the result string was SomeOtherAction.class.toString(), it will be chained
> to the SomeOtherAction.
> To change default result type of action from chain to other result type, just
> prepend result type in result string, for example: "redirect:edit.action".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
