...
The Logon mapping uses a different return type for "success" (the default result code). The redirect-action takes the name of an Action as a parameter, and then issues a client-side redirect to the new action. As a result, the URI on the browser's location bar will change.
Configuring Global Results
It's not unusual for mappings to share a need for the same result. For example, if your application is secure, then many mappings might need to return "login" if the security check fails. Rather than define a common result in every action mapping, the framework lets you define global results.
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<global-results>
<result name="login" type="redirect-action">Login</result>
<result name="unauthorized" type="action-chain">Unauthorized</result>
</global-results>
|
| Note | ||
|---|---|---|
| ||
Because global results are searched after local results, you can override any global result mapping by creating a local result mapping of the same name. Results can indicate resources using relative or absolute URIs. Because you may not know the context in which a result is being invoked, it's best to use absolute paths for global results. |
Summary
The framework offers a variety of result types. An Action can select the appropriate result by name, without actually knowing what result type will be rendered. If a result can be used by multiple action mappings, it can be defined once as a global result.
...