View"
From Documentation
m |
|||
| Line 3: | Line 3: | ||
A view could be anything. ZEST simply forwards the request to the given URI (by invoking <code>javax.servlet.RequestDispatcher</code>). | A view could be anything. ZEST simply forwards the request to the given URI (by invoking <code>javax.servlet.RequestDispatcher</code>). | ||
| − | Since all [[ZEST Essentials/EL Expressions/Implicit | + | Since all [[ZEST Essentials/EL Expressions/Implicit Objects|implicit objects]], except [[ZEST Essentials/EL Expressions/Implicit Objects/request|request]]<ref>The request is not stored since it is supported by almost all technologies. For example, in ZUML, you could use <code>execution</code> to retrieve it.</ref>, are stored as the request's attributes, they can be retrieved easily in the targeted view. For example, you could retrieve the action with an EL expression as follows, if the technology supports EL expressions, such as ZUML and JSP. |
<source lang="xml"> | <source lang="xml"> | ||
Latest revision as of 06:24, 14 March 2011
A view could be anything. ZEST simply forwards the request to the given URI (by invoking javax.servlet.RequestDispatcher).
Since all implicit objects, except request[1], are stored as the request's attributes, they can be retrieved easily in the targeted view. For example, you could retrieve the action with an EL expression as follows, if the technology supports EL expressions, such as ZUML and JSP.
<p>${action.message}</p>
- ↑ The request is not stored since it is supported by almost all technologies. For example, in ZUML, you could use
executionto retrieve it.
Version History
| Version | Date | Content |
|---|---|---|