Spring/spring-webflow
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated to new version of Spring Build that has syntax highlighting

Browse Source
This commit is contained in:
Ben Hale
2008-05-20 09:29:59 +00:00
parent 170c14c4ca
commit 5045de52e9
12 changed files with 41 additions and 747 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
spring-webflow-reference/src/el.xml
View File

@@ -65,7 +65,7 @@
Such expressions are dynamically evaluated by the EL and should not be enclosed in delimiters like <code>${}</code> or <code>#{}</code>.
For example:
</para>
<programlisting type="xml"><![CDATA[
<programlisting language="xml"><![CDATA[
<evaluate expression="searchCriteria.nextPage()" />]]>
</programlisting>
<para>
@@ -84,7 +84,7 @@
Each eval block is explictly delimited with the <code>${}</code> delimiters.
For example:
</para>
<programlisting type="xml"><![CDATA[
<programlisting language="xml"><![CDATA[
<view-state id="error" view="error-${externalContext.locale}.xhtml" />]]>
</programlisting>
<para>
@@ -110,7 +110,7 @@
Use <code>flowScope</code> to assign a flow variable.
Flow scope gets allocated when a flow starts and destroyed when the flow ends.
</para>
<programlisting type="xml"><![CDATA[
<programlisting language="xml"><![CDATA[
<evaluate expression="searchService.findHotel(hotelId)" result="flowScope.hotel" />]]>
</programlisting>
</sect2>
@@ -121,7 +121,7 @@
View scope gets allocated when a <code>view-state</code> enters and destroyed when the state exits.
View scope is <emphasis>only</emphasis> referenceable from within a <code>view-state</code>.
</para>
<programlisting type="xml"><![CDATA[
<programlisting language="xml"><![CDATA[
<on-render>
<evaluate expression="searchService.findHotels(searchCriteria)" result="viewScope.hotels"
result-type="dataModel" />
@@ -134,7 +134,7 @@
Use <code>requestScope</code> to assign a request variable.
Request scope gets allocated when a flow is called and destroyed when the flow returns.
</para>
<programlisting type="xml"><![CDATA[
<programlisting language="xml"><![CDATA[
<set name="requestScope.hotelId" value="requestParameters.id" type="long" />]]>
</programlisting>
</sect2>
@@ -144,7 +144,7 @@
Use <code>flashScope</code> to assign a flash variable.
Flash scope gets allocated when a flow starts, cleared after every view render, and destroyed when the flow ends.
</para>
<programlisting type="xml"><![CDATA[
<programlisting language="xml"><![CDATA[
<set name="flashScope.statusMessage" value="'Booking confirmed'" />]]>
</programlisting>
</sect2>
@@ -155,7 +155,7 @@
Conversation scope gets allocated when a top-level flow starts and destroyed when the top-level flow ends.
Conversation scope is shared by a top-level flow and all of its subflows.
</para>
<programlisting type="xml"><![CDATA[
<programlisting language="xml"><![CDATA[
<evaluate expression="searchService.findHotel(hotelId)" result="conversationScope.hotel" />]]>
</programlisting>
</sect2>
@@ -164,7 +164,7 @@
<para>
Use <code>requestParameters</code> to access a client request parameter:
</para>
<programlisting type="xml"><![CDATA[
<programlisting language="xml"><![CDATA[
<set name="requestScope.hotelId" value="requestParameters.id" type="long" />]]>
</programlisting>
</sect2>
@@ -173,7 +173,7 @@
<para>
Use <code>currentEvent</code> to access attributes of the current <code>Event</code>:
</para>
<programlisting type="xml"><![CDATA[
<programlisting language="xml"><![CDATA[
<evaluate expression="booking.guests.add(currentEvent.guest)" />]]>
</programlisting>
</sect2>
@@ -182,7 +182,7 @@
<para>
Use <code>currentUser</code> to access the authenticated <code>Principal</code>:
</para>
<programlisting type="xml"><![CDATA[
<programlisting language="xml"><![CDATA[
<evaluate expression="bookingService.createBooking(hotelId, currentUser.name)"
result="flowScope.booking" />]]>
</programlisting>
@@ -193,7 +193,7 @@
Use <code>messageContext</code> to access a context for retrieving and creating flow execution messages, including error and success messages.
See the <code>MessageContext</code> Javadocs for more information.
</para>
<programlisting type="xml"><![CDATA[
<programlisting language="xml"><![CDATA[
<evaluate expression="bookingValidator.validate(booking, messageContext)" />]]>
</programlisting>
</sect2>
@@ -202,7 +202,7 @@
<para>
Use <code>resourceBundle</code> to access a message resource.
</para>
<programlisting type="xml"><![CDATA[
<programlisting language="xml"><![CDATA[
<set name="flashScope.successMessage" value="resourceBundle.successMessage" />]]>
</programlisting>
</sect2>
@@ -232,7 +232,7 @@
Use <code>externalContext</code> to access the client environment, including user session attributes.
See the <code>ExternalContext</code> API JavaDocs for more information.
</para>
<programlisting type="xml"><![CDATA[
<programlisting language="xml"><![CDATA[
<evaluate expression="searchService.suggestHotels(externalContext.sessionMap.userProfile)"
result="viewScope.hotels" />]]>
</programlisting>
@@ -244,14 +244,14 @@
When assigning a variable in one of the flow scopes, referencing that scope is required.
For example:
</para>
<programlisting type="xml"><![CDATA[
<programlisting language="xml"><![CDATA[
<set name="requestScope.hotelId" value="requestParameters.id" type="long" />]]>
</programlisting>
<para>
When simply accessing a variable in one of the scopes, referencing the scope is optional.
For example:
</para>
<programlisting type="xml"><![CDATA[
<programlisting language="xml"><![CDATA[
<evaluate expression="entityManager.persist(booking)" />]]>
</programlisting>
<para>