View"

From Documentation
m (Created page with "{{ZESTEssentialsPageHeader}} =Version History= {{LastUpdated}} {| border='1px' | width="100%" ! Version !! Date !! Content |- |   |   |   |} {{ZESTEssentialsPage...")
 
m
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
{{ZESTEssentialsPageHeader}}
 
{{ZESTEssentialsPageHeader}}
 +
 +
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 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">
 +
<p>${action.message}</p>
 +
</source>
 +
 +
<blockquote>
 +
----
 +
<references/>
 +
</blockquote>
  
 
=Version History=
 
=Version History=

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>

  1. The request is not stored since it is supported by almost all technologies. For example, in ZUML, you could use execution to retrieve it.

Version History

Last Update : 2011/03/14


Version Date Content
     



Last Update : 2011/03/14

Copyright © Potix Corporation. This article is licensed under GNU Free Documentation License.