[WW-1515] Support code-behind design and default results

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.1
• Fix Version/s: 2.0.2
• Component/s: Dispatch Filter, Plugin - Mechanism, XML Configuration
• Assignee: Donald J. Brown
• Reporter: Donald J. Brown
• Created: 19/Nov/06 05:02
• Updated: 28/Oct/12 22:11
• Resolved: 19/Nov/06 05:06

Description

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.