* How do you manage navigation and conversational states?
* How do you facilitate modularization and reuse?
In Spring Web Flow, a ''web flow'' answers all of the above questions: it captures navigational rules allowing the Spring Web Flow execution engine to manage a conversation and the associated state. At the same time,timn a2005 ''webthe flow''project was introduced into the Spring portfolio by Keith Donald and grew into the official Spring sub-project it is now. The first production ready 1.0 release was made on 2006-10-26. Version 2.0, first released on 2008-04-29, saw a reusablemajor internal reorganization of the framework to allow better integration webwith application[[JavaServer moduleFaces]].
Since version 2.0, Spring Web Flow also introduces other additional features supporting the construction of ''rich'' web applications, such as AJAX support and tight integration with [[JavaServer Faces]].
==History==
The Spring Web Flow project started as a simple extension to the Spring Web MVC framework providing ''web flow'' functionality, developed by Erwin Vervaet in 2004. In 2005 the project was introduced into the Spring portfolio by Keith Donald and grew into the official Spring sub-project it is now. The first production ready 1.0 release was made on 2006-10-26. Version 2.0, first released on 2008-04-29, saw a major internal reorganization of the framework to allow better integration with [[JavaServer Faces]].
