...
Additional Result Types can be created and plugged into an application by implementing the com.opensymphony.xwork2.Result
interface. Custom Result Types might include generating an email or JMS message, generating images, and so forth.
Default Parameters
To minimize configuration, Results can be configured with a single value, which will be converted into a parameter, and each Result can specify which parameter this value should be set as. For example, here is a result defined in XML that uses a default parameter:
Code Block | ||
---|---|---|
| ||
<result type="freemarker">foo.fm</result>
|
That is the equivalent to this:
Code Block | ||
---|---|---|
| ||
<result type="freemarker">
<param name="location">foo.vm</param>
</result>
|
Since probably 95% of your actions won't need results that contain multiple parameters, this little shortcut saves you a significant amount of configuration. It also follows that if you have specified the default parameter, you don't need to set the same parameter as a specifically-named parameter.
Registering Result Types
All Result Types are plugged in via the Result Configuration.
...