You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Don Brown (JIRA)" <ji...@apache.org> on 2006/11/19 06:03:57 UTC
[jira] Created: (WW-1515) Support code-behind design and default
results
Support code-behind design and default results
----------------------------------------------
Key: WW-1515
URL: http://issues.apache.org/struts/browse/WW-1515
Project: Struts 2
Issue Type: New Feature
Components: Configuration, Dispatch, Plugins
Affects Versions: 2.0.1
Reporter: Don Brown
Assigned To: Don Brown
Fix For: 2.0.2
There are two very common cases where we could replace configuration with conventions:
- pages that have a template/jsp but no Action class
- Actions that go to a result with the same name as the action e.g. FooAction -> foo.jsp
We should have a plugin that uses the new UnknownHandler hook in XWork 2 to fill in these two common unknown cases with convention-based configuration. For example, if you have a foo.jsp, but don't have an action, the plugin should detect the jsp and front the file with a no-op Action. In the second case, the plugin should guess the result by scanning for files of the same name and creating the result on the fly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (WW-1515) Support code-behind design and default
results
Posted by "Don Brown (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/WW-1515?page=all ]
Don Brown resolved WW-1515.
---------------------------
Resolution: Fixed
Fixed with the Codebehind Plugin
> Support code-behind design and default results
> ----------------------------------------------
>
> Key: WW-1515
> URL: http://issues.apache.org/struts/browse/WW-1515
> Project: Struts 2
> Issue Type: New Feature
> Components: Configuration, Dispatch, Plugins
> Affects Versions: 2.0.1
> Reporter: Don Brown
> Assigned To: Don Brown
> Fix For: 2.0.2
>
>
> There are two very common cases where we could replace configuration with conventions:
> - pages that have a template/jsp but no Action class
> - Actions that go to a result with the same name as the action e.g. FooAction -> foo.jsp
> We should have a plugin that uses the new UnknownHandler hook in XWork 2 to fill in these two common unknown cases with convention-based configuration. For example, if you have a foo.jsp, but don't have an action, the plugin should detect the jsp and front the file with a no-op Action. In the second case, the plugin should guess the result by scanning for files of the same name and creating the result on the fly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira