From da0fc97c8ef55f49bc0d001441f57589326d3d16 Mon Sep 17 00:00:00 2001 From: Keith Donald Date: Sun, 1 Apr 2007 18:14:36 +0000 Subject: [PATCH] removed obsolete stuff --- .../shippingrate/src/main/webapp/index.jsp | 4 -- .../docs/reference/src/practical.xml | 40 ++----------------- 2 files changed, 4 insertions(+), 40 deletions(-) diff --git a/spring-webflow-samples/shippingrate/src/main/webapp/index.jsp b/spring-webflow-samples/shippingrate/src/main/webapp/index.jsp index a6097508..d6ee283f 100644 --- a/spring-webflow-samples/shippingrate/src/main/webapp/index.jsp +++ b/spring-webflow-samples/shippingrate/src/main/webapp/index.jsp @@ -33,10 +33,6 @@ Implementing a wizard using Spring Web Flow. -

- Note: this sample has been tested successfully on Internet Explorer 6 and 7, Firefox 2 and Safari 2. - There are currently known Javascript issues with use on Firefox 1.5. -

diff --git a/spring-webflow/docs/reference/src/practical.xml b/spring-webflow/docs/reference/src/practical.xml index 3df53df3..d05b5eed 100644 --- a/spring-webflow/docs/reference/src/practical.xml +++ b/spring-webflow/docs/reference/src/practical.xml @@ -611,13 +611,6 @@ public BirthDateFormAction() { After the initial index.jsp subsequent pages are loaded in an Ajax manner without reloading the entire page. - - - This sample has been tested successfully on Internet Explorer 6 and 7, - Firefox 2.0, and Safari 2. There are known Javascript issues - with use on Firefox 1.5. - - The Ajax requests are done with the help of the Prototype @@ -1305,7 +1298,7 @@ if (data != null && data.length() > 0) { Itemlist-alternate Web Flow The Itemlist-alternate web flow (/WEB-INF/itemlist-alternate.xml) - has functionality equivalent to that of itemlist but instead uses + has functionality equivalent to that of itemlist but instead uses a subflow for selecting individual items. The "addItem" state is a subflow state invoking an inline flow called "item" (also defined in itemlist-alternate.xml) @@ -1328,38 +1321,13 @@ if (data != null && data.length() > 0) { <end-state id="finish"> <output-mapper> - <mapping source="flowScope.item" target="item" /> + <mapping source="requestParameters.data" target="item" /> </output-mapper> </end-state> With the above declarations we see how a subflow can pass output - parameters back to its parent flow. The remaining question is - what sets "flowScope.item" which appears for the first time - in the end state of the subflow? - - - The answer lies in the "mapItemAction" bean invoked between the - view state and the end state in the subflow: - -<action-state id="mapItem"> - <action bean="mapItemAction" /> - <transition on="success" to="finish" /> -</action-state> - - The mapItemAction bean was defined in the itemlist-servlet.xml web context - and is an istance of Web Flow's AttributeMapperAction. The purpose - of AttributeMapperAction is to invoke an AttributeMapper and to perform - mappings between two attribute sources. The AttributeMapper with which - the mapItemAction bean is configured is an instance of DataMapper. It - adds the following mapping: - -addMapping(mapping.source("requestParameters.data").target("flowScope.item").value()); - - With this declaration in place each time the AttributeMaperAction is - invoked it will create the flowScoped variable "item" based on the value - of the "data" request parameter. Note that AttributeMapper is - Web Flow API for the <attribute-mapper> declarations used above - to pass data from the inner subflow to the parent flow. + parameters back to its parent flow - in this case the 'data' request parameter + is passed back as an output parameter. Once the inner subflow flow has completed the item is passed to the parent flow