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

Add Gradle build

Browse Source 
- Add gradle build script
- Remove spring-build/
- Remove build-spring-webflow/
- Remove ivy.xml, pom.xml, template.mf
- Remove eclipse  metadata
- Remove RichFacesAjaxHandler.java
- Create src/dist and add changelog.txt, readme.txt

Dependency changes:
- EBR dependency -> Maven-central dependencies
- el-api 1.0 -> 2.2.0
- ognl 2.6.9 -> 2.6.11
- org.jboss.el -> tomcat-jasper-el 7.0.27
This commit is contained in:
Rossen Stoyanchev
2012-05-24 16:30:57 -04:00
parent b4847ef49b
commit 4e81930b72
162 changed files with 659 additions and 9157 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
src/api/overview.html Normal file
View File

@@ -0,0 +1,28 @@
<html>
<body>
<p align="center">
<img src="http://static.springframework.org/spring-webflow/images/spring-webflow.jpg"><br>
The public Java Documentation for the Spring Web Flow project.
</p>
<p>Spring Web Flow facilitates building web applications that require guided navigation -- e.g. a shopping cart, flight check-in, a loan application, and many others. In contrast to stateless, free-form navigation such use cases have a clear start and end point, one or more screens to go through in a specific order, and a set of changes that are not finalized to the end.</p>
<p>A distinguishing feature is the ability to define a <strong>flow definition</strong> consisting of <em>states</em>, <em>transitions</em>, and <em>data</em>. For example, view states correspond to the individual screens of the flow while transitions are caused by events resulting from the click of a button or a link. Data may be stored in scopes such as <em>flash</em>, <em>view</em>, <em>flow</em>, and others. Scoped data is cleared when it is no longer in scope.</p>
<p>In REST terms a flow represents as a single resource. The same URL used to start the flow is also the URL used to step through the flow (there is also an execution key uniquely identifying the current flow instance). As a result of this approach navigation remains encapsulated in the flow definition.</p>
<p>Some key benefits of using Spring Web Flow:</p>
<ul>
<li>A flow abstraction to model <em>"long conversations"</em> in web applications</li>
<li>Proper encapsulation for navigation rules</li>
<li>Multiple scopes in which to keep data</li>
<li>Automatic use of the POST/REDIRECT/GET pattern to avoid browser warnings</li>
<li>Impossible to return to completed flow sessions via browser back button</li>
<li>Rapid prototyping of flow requirements</li>
<li>Development mode in which flow definition changes are detected on the fly</li>
<li>IDE visualization for flow definitions</li>
<li>Much more...</li>
</ul>
</body>
</html>