Solution: Spring supports defining a flow either by java or XML.

Solution: Spring Web Flow builds in several state types, including view state, action state, decision state, subflow state, and end state.

Solution: To manage your web UI flows with Spring Web Flow, you need the Spring Web Flow distribution (e.g.,v2.0.8) on your CLASSPATH.

Solution: Spring Web Flow supports using Unified EL (used in JSF 1.2 and JSP 2.1) and Object-Graph Navigation Language (OGNL), which is used in Tapestry, WebWork, and other frameworks, as its expression language.

Solution: The FlowHandlerMapping follows a convention to create URL path mappings from the ids of registered flow definitions.

Solution: Spring Web Flow offers an XML–based flow definition language that can be validated by Spring Web Flow XSD and supported by Spring IDE or SpringSource Tool Suite (STS).

Solution: You can use the on-render element to trigger an action for a view state before its view renders.

Solution: You have to start the URLs with the variable ${flowExecutionUrl} to trigger a flow execution. This variable will be evaluated by Spring Web Flow at runtime.

Solution: By default, Tomcat and Jetty (and the Maven Jetty plugin configured for this code) listen on port 8080.

Solution: Implement the Serializable interface, as its instances may need to be persisted in sessions.