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

Fixed some DocBook DTD compliance issues.

Browse Source
This commit is contained in:
Erwin Vervaet
2007-04-10 19:13:11 +00:00
parent b2d4f9d0c8
commit d3e8d8dd23
4 changed files with 2238 additions and 2222 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
spring-webflow/docs/reference/src/flow-definition.xml
View File

@@ -1263,9 +1263,11 @@
</table>
<para>
<note>
The above other points in a flow where actions may be executed do not
allow you to execute a state transition in response to the action result event.
If you need such flow control you must execute the action from within an action state.
<para>
The above other points in a flow where actions may be executed do not
allow you to execute a state transition in response to the action result event.
If you need such flow control you must execute the action from within an action state.
</para>
</note>
</para>
</sect3>
@@ -1967,13 +1969,15 @@
</para>
<para>
<note>
<emphasis>Caution</emphasis>: flow definitions should <emphasis>not</emphasis> be vehicles for
business logic. In this case the decision made was controller logic, reasoning on a
pre-calculated value to decide what step of the flow to transition to next. That is the kind of logic that
should be in a flow definition. In contrast, having the state <emphasis>itself</emphasis> embed
the business rule defining how shipping status is calculated is a misuse.
Instead, push such a calculation into application code where it belongs and <emphasis>instruct</emphasis>
the flow to invoke that code using an action.
<para>
<emphasis>Caution</emphasis>: flow definitions should <emphasis>not</emphasis> be vehicles for
business logic. In this case the decision made was controller logic, reasoning on a
pre-calculated value to decide what step of the flow to transition to next. That is the kind of logic that
should be in a flow definition. In contrast, having the state <emphasis>itself</emphasis> embed
the business rule defining how shipping status is calculated is a misuse.
Instead, push such a calculation into application code where it belongs and <emphasis>instruct</emphasis>
the flow to invoke that code using an action.
</para>
</note>
</para>
</sect3>

20
spring-webflow/docs/reference/src/flow-executor.xml
View File

@@ -229,11 +229,13 @@
</para>
<para>
<note>
The <literal>alwaysRedirectOnPause</literal> attribute determines if
a flow execution redirect occurs automatically each time an execution pauses
(automated <literal>POST+REDIRECT+GET</literal> behavior).
Setting this attribute to false will disable the <emphasis>default 'true' behavior</emphasis>
where a flow execution redirect always occurs on pause.
<para>
The <literal>alwaysRedirectOnPause</literal> attribute determines if
a flow execution redirect occurs automatically each time an execution pauses
(automated <literal>POST+REDIRECT+GET</literal> behavior).
Setting this attribute to false will disable the <emphasis>default 'true' behavior</emphasis>
where a flow execution redirect always occurs on pause.
</para>
</note>
</para>
</sect2>
@@ -354,9 +356,11 @@
<literal>org.springframework.webflow.executor.support.FlowExecutorArgumentExtractor</literal>
strategy.
<note>
The various flow controllers typically do not use this strategy directly but instead use a
convenient <literal>FlowExecutorArgumentHandler</literal> implementation that takes care
of argument extraction as well as exposing responsibilities (in callback URLs).
<para>
The various flow controllers typically do not use this strategy directly but instead use a
convenient <literal>FlowExecutorArgumentHandler</literal> implementation that takes care
of argument extraction as well as exposing responsibilities (in callback URLs).
</para>
</note>
</para>
<para>

28
spring-webflow/docs/reference/src/overview.xml
View File

@@ -104,13 +104,15 @@
</para>
<para>
<note>
Spring Web Flow, like Spring, is a <emphasis>layered</emphasis> framework,
packaged in a manner that allows teams to use the parts they need and nothing else.
For example, one team might use Spring Web Flow in a Servlet environment with Spring MVC
and thus require the Spring MVC integration. Another team might use SWF in a Portlet
environment, and thus require the Portlet MVC integration. Another team might mix and match.
A major benefit of SWF is that it allows you to define reusable, self-contained controller
modules that can execute in <emphasis>any</emphasis> environment.
<para>
Spring Web Flow, like Spring, is a <emphasis>layered</emphasis> framework,
packaged in a manner that allows teams to use the parts they need and nothing else.
For example, one team might use Spring Web Flow in a Servlet environment with Spring MVC
and thus require the Spring MVC integration. Another team might use SWF in a Portlet
environment, and thus require the Portlet MVC integration. Another team might mix and match.
A major benefit of SWF is that it allows you to define reusable, self-contained controller
modules that can execute in <emphasis>any</emphasis> environment.
</para>
</note>
</para>
</sect1>
@@ -613,11 +615,13 @@
</table>
<para>
<note>
As described above, some subsystem packages are optional depending on your use of the
subsystem. For example, use of Spring Web Flow in a Servlet environment entails use of
the <literal>ExternalContext</literal> context.servlet package which requires the
Servlet API to be in the classpath. In this case the context.portlet package is not
used and the Portlet API is not required.
<para>
As described above, some subsystem packages are optional depending on your use of the
subsystem. For example, use of Spring Web Flow in a Servlet environment entails use of
the <literal>ExternalContext</literal> context.servlet package which requires the
Servlet API to be in the classpath. In this case the context.portlet package is not
used and the Portlet API is not required.
</para>
</note>
</para>
<para>

4388
spring-webflow/docs/reference/src/practical.xml
View File

File diff suppressed because it is too large Load Diff