THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Most use cases can be divided into two phases. First, we need to change or query the application's state, and then we need to present an updated view of the application. The Action class manages the application's state, and the Result Type manages the view.
Predefined Result Types
The framework provides several implementations of the com.opensymphony.xwork2.Result interface, ready to use in your own applications.
Used for Action Chaining | ||
Used for JSP integration | ||
Used for FreeMarker integration | ||
Used to control special HTTP behaviors | ||
Used to redirect to another URL | ||
Used to redirect to another Action | ||
Used to stream an InputStream back to the browser (usually for file downloads) | ||
Used for Velocity integration | ||
Used for XML/XSLT integration | ||
Used to display the raw content of a particular page (i.e jsp, HTML) | ||
Used to provide Tiles integration | ||
Used for JasperReports Tutorial integration | Optional, third-party plugin |
Additional Result Types can be created and plugged into an application by implementing the com.opensymphony.xwork.Result interface. Custom Result Types might include generating an email or JMS message, generating images, and so forth.
Registering Result Types
All Result Types are plugged in via the Result Configuration.