View Source

h1. Spring Web Flow 2.5, Spring Security 5.1, and ICEfaces 3.3


h3. About Spring Web Flow

[Spring Web Flow||Spring Web Flow 2.5 Documentation] is a library that extends Spring MVC to user defined "controllers using a domain-specific-language." Web Flow is appropriately used when several actions need to be performed in order for a greater action to be performed (booking a hotel, or a flight for instance).

h3. About Spring Security

Spring Security 5.1 provides an API for configuring authentication and authorization. Authentication is possible against any number of repositories and databases. Authorization is applied at either the web resource level using Servlet Filters and/or at the business/service method level using aspects and annotations.

Go directly to the portion of this tutorial dealing with [Spring Security 5.1 configuration|#security_config_xml].

h3. About This Tutorial

This tutorial borrows heavily on existing JSF tutorials for Spring Web Flow, and is an evolution of the tutorial for [integrating ICEfaces 3.x with Spring Web Flow 2.3.1|ICE:Spring Web Flow 2.3.1].

The purpose of this tutorial is to demonstrate how application developers can use both Spring Webflow 2.5 and ICEfaces 3.3.0 in the same application. Both technologies leverage the Servlet API. Understanding how the various parts of the web.xml file are organized to accomodate both frameworks is essential to understanding this tutorial and being able to extend it to meet your own requirements.


This tutorial uses Spring Web Flow 2.5, Spring Security 5.1, Spring Core 5.1, JSF 2.2.16 and ICEfaces 3.3.0_P07. Additional libraries are needed to support these frameworks and have been listed as dependencies in the tutorial's pom.xml file.

h3. Tutorial Use Case

The simple business case for this tutorial is the Spring Web Flow standard "booking application". Users can search for hotels and, after authenticating, book a room. Authenticated users can also review their bookings. This tutorial borrows heavily from the Spring Web Flow sample booking application.

h3. Issue with null ViewId and WindowID

There is an issue with the Spring implementation of the Lifecycle that affects the operation of ICEfaces. The ICEfaces BridgeSetup class uses a JSF PhaseListener to restore certain scope variables into the request map. Spring webflow applications, by default, use a POST->Redirect->GET pattern for navigation, but during the subsequent GET operation, the Spring lifecycle implementation does not appear to be executing the phase listeners during the RESTORE_VIEW phase. Side effects of this problem are the following symptoms:

1) Console messages of the following form:

{quote}SEVERE - Missing view ID attribute. Request map cleared prematurely.

SEVERE - Missing window ID attribute. Request map cleared prematurely.
{quote}2) NPE trying to rewrite a null viewID into the document:

at org.icefaces.impl.util.DOMUtils.isWhitespaceText(
at org.icefaces.impl.util.DOMUtils.printNode(
at org.icefaces.impl.util.DOMUtils.printNode(
at org.icefaces.impl.util.DOMUtils.printNode(

While the booking tutorial does not take advantage of windowScope, it is clear that functionality is reduced. There is a solution, and that is to use a WebflowListener to duplicate the missing PhaseListener functionality. The spring-booking-tutorial uses the (which is an instance of FlowExecutionListenerAdapter) class to this end. You can download a copy of this WebflowListener directly from the link above, and it is also contained and configured in the tutorial. Configuration of the WebflowListener is shown in the *webflow-config.xml* configuration section below.

h3. Building the Tutorial WAR

Follow the [general instructions for building any of the tutorials|ICE:Tutorials#Setup].

h3. Configuration Areas

There isn't a perfect delineation between the Spring Web MVC, Web Flow and Security configurations, but they are mostly separated into their own separate files, with each requiring some entries in the _web.xml_.

# [Configure _web.xml_ for Spring (Core, Web Flow, and Security)|#web_xml]
# [Configure _web-application-config.xml_|#web_application_config_xml]
# [Configure _webflow-config.xml_|#webflow_config_xml]
# [Configure _webmvc-config.xml_|#webmvc_config_xml]
# [Configure _security-config.xml_|#security_config_xml]
# [Configure _data-access-config.xml_|#data_access_config_xml]


h3. Part 1: Configure _web.xml_ for Spring

The _web.xml_ below provides configuration parameters for JSF, filter configurations for Spring security, Spring and JSF Servlet declarations and listeners.
<web-app version="3.0"

<!-- Enables JSF debug output during development -->

<!-- Best practice with ICEfaces -->

<!-- Causes Facelets to refresh templates during development -->

<!-- Use JSF view templates saved as *.xhtml, for use with Facelets -->

<!-- The master configuration file for this Spring web application -->

<!-- Declare Spring Security Facelets tag library -->

<!-- Enforce UTF-8 Character Encoding -->


<!-- Enables Spring Security -->


<!-- Loads the Spring web application context -->

<!-- The front controller of this Spring Web application, responsible for handling all application requests -->
<servlet-name>Spring MVC Dispatcher Servlet</servlet-name>

<!-- Map all /spring requests to the Dispatcher Servlet for handling -->
<servlet-name>Spring MVC Dispatcher Servlet</servlet-name>

<!-- Faces Servlet -->
<servlet-name>Faces Servlet</servlet-name>

<!-- Faces Servlet Mapping -->
<servlet-name>Faces Servlet</servlet-name>

<!-- Resolve the missing PNG entry issue on old servers such as WAS7 -->

<!-- Welcome File Configuration -->



h3. Part 2: Configure _web-application-config.xml_

The master configuration file for Spring, as referenced in the _web.xml_ by the contextConfigLocation context-param. This file imports all the other Spring configuration files, to better separate the separate concerns into smaller more manageable files, for webmvc, webflow, database, security.

{code:xml|title=/WEB-INF/config/web-application-config.xml}<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns=""

<!-- Scans for application @Components to deploy -->
<context:component-scan base-package="" />

<!-- Imports the configurations of the different infrastructure systems of the application -->
<import resource="webmvc-config.xml" />
<import resource="webflow-config.xml" />
<import resource="data-access-config.xml" />
<import resource="security-config.xml" />


h3. Part 3: Configure _webflow-config.xml_

This step provides an overview of what needs to go into the Spring Web Flow configuration file to integrate well with ICEfaces 3.x. The configuration directs Spring Web Flow to look in the /WEB-INF/flows/\**/*\-flow.xml pattern for web flow declarations. The tutorial application has two of these files which manage the *main* use case of hostel searching and selection, and the *booking* case for creating a reservation. There are three FlowExecutionListener declarations: FlowFacesContextLifecycleListener, for managing the FacesContext; SecurityFlowExecutionListener, for security integration; and our WebflowListener, for JSF viewId and ICEfaces windowId management.

{code:xml|title=/WEB-INF/config/webflow-config.xml}<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns=""

<!-- Executes flows: the central entry point into the Spring Web Flow system -->
<webflow:flow-executor id="flowExecutor">
<webflow:listener ref="facesContextListener"/>
<webflow:listener ref="securityFlowExecutionListener" />
<webflow:listener ref="icefacesFlowListener" />

<!-- The registry of executable flow definitions -->
<webflow:flow-registry id="flowRegistry" flow-builder-services="facesFlowBuilderServices" base-path="/WEB-INF/flows">
<webflow:flow-location-pattern value="/**/*-flow.xml" />

<!-- Configures the Spring Web Flow JSF integration -->
<faces:flow-builder-services id="facesFlowBuilderServices" development="true" />

<!-- Installs a listener that creates and releases the FacesContext for each request. -->
<bean id="facesContextListener" class="org.springframework.faces.webflow.FlowFacesContextLifecycleListener"/>

<!-- Installs a listener to apply Spring Security authorities -->
<bean id="securityFlowExecutionListener" class="" />

<!-- Set the viewId and windowId after a POST-Redirect-GET -->
<bean id="icefacesFlowListener" class="" />


h3. Part 4: Configure _webmvc-config.xml_

This configuration file includes the basic setup of resolving request paths to flow and view definitions, and resolving their Facelet view definition files. It declares the relevant JSF view and controller objects from Spring MVC, and JSF flow handler from Spring Web Flow.

{code:xml|title=/WEB-INF/config/webmvc-config.xml}<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns=""

<faces:resources />

<!-- Maps request paths to flows in the flowRegistry; e.g. a path of /hotels/booking looks for a flow with id "hotels/booking" -->
<bean class="org.springframework.webflow.mvc.servlet.FlowHandlerMapping">
<property name="order" value="1"/>
<property name="flowRegistry" ref="flowRegistry" />
<property name="defaultHandler">
<!-- If no flow match, map path to a view to render; e.g. the "/intro" path would map to the view named "intro" -->
<bean class="org.springframework.web.servlet.mvc.UrlFilenameViewController" />

<!-- Maps logical view names to Facelet templates in /WEB-INF (e.g. 'search' to '/WEB-INF/search.xhtml' -->
<bean id="faceletsViewResolver" class="org.springframework.web.servlet.view.UrlBasedViewResolver">
<property name="viewClass" value="org.springframework.faces.mvc.JsfView"/>
<property name="prefix" value="/WEB-INF/" />
<property name="suffix" value=".xhtml" />

<!-- Dispatches requests mapped to org.springframework.web.servlet.mvc.Controller implementations -->
<bean class="org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter" />

<!-- Dispatches requests mapped to flows to FlowHandler implementations -->
<bean class="org.springframework.faces.webflow.JsfFlowHandlerAdapter">
<property name="flowExecutor" ref="flowExecutor" />



h3. Part 5: Configure _security-config.xml_

Configuring Spring Security to work properly with ICEfaces 3 requires configurations not included in other JSF-based Spring Webflow tutorials. This is due to the design decision to leverage Spring Security's configurable "redirectStrategy" property. We explicitly configure the redirectStrategy used by Spring Security to send AJAX redirects if the request is AJAX driven (contains an AJAX header).

{code:xml|title=/WEB-INF/config/security-config.xml}<?xml version="1.0" encoding="UTF-8"?>
<beans:beans xmlns=""

<!-- Configure Spring Security -->
<http auto-config="true"

<form-login login-page="/spring/login"
default-target-url="/spring/main" always-use-default-target="true"
authentication-failure-url="/spring/login?login_error=1" />

<!-- When using custom filters, please make sure the positions do not conflict with default filters.
Alternatively you can disable the default filters by removing the corresponding child elements from
http and avoiding the use of http auto-config='true'. -->

<custom-filter ref="exceptionTranslationFilter" before="FILTER_SECURITY_INTERCEPTOR" />

<logout logout-url="/spring/logout" logout-success-url="/spring/logoutSuccess" invalidate-session="true"/>
<intercept-url pattern="/secure" method="POST" access="hasRole('ROLE_SUPERVISOR')"/>
<csrf disabled="true"/>

<beans:bean id="passwordEncoder" class="">
<beans:constructor-arg value="MD5"/>

Define local authentication provider, a real app would use an external provider (JDBC, LDAP, CAS, etc)

usernames/passwords are:
<user name="keith" password="417c7382b16c395bc25b5da1398cf076"
<user name="erwin" password="12430911a8af075c6f41c6976af22b09"
<user name="jeremy" password="57c6cbff0d421449be820763f03139eb" authorities="ROLE_USER"/>
<user name="scott" password="942f2339bf50796de535a384f0d1af3e" authorities="ROLE_USER"/>
<password-encoder ref="passwordEncoder"/>

<beans:bean id="sessionManagementFilter"
<beans:constructor-arg name="securityContextRepository" ref="httpSessionSecurityContextRepository" />
<beans:property name="invalidSessionStrategy" ref="jsfInvalidSessionStrategy" />

<beans:bean id="jsfInvalidSessionStrategy" class="">
<beans:constructor-arg name="invalidSessionUrl" value="/general/logins/sessionExpired.jsf" />

<!-- -->
<beans:bean id="exceptionTranslationFilter" class="">
<beans:property name="accessDeniedHandler" ref="jsfAccessDeniedHandler"/>
<beans:constructor-arg name="authenticationEntryPoint" ref="authenticationEntryPoint"/>

<beans:bean id="jsfAccessDeniedHandler" class="">
<beans:property name="loginPath" value="/spring/login" />
<beans:property name="contextRelative" value="true" />

<beans:bean id="authenticationEntryPoint" class="">
<beans:property name="loginFormUrl" value="/spring/login"/>
<beans:property name="redirectStrategy" ref="jsfRedirectStrategy" />
</beans:bean >

<beans:bean id="jsfRedirectStrategy" class=""/>
<beans:bean id="httpSessionSecurityContextRepository" class=""/>



h3. Part 6: Configure _data-access-config.xml_

Configured to use HSQLDB via Hibernate.

{code:xml|title=/WEB-INF/config/data-access-config.xml}<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns=""

<!-- Instructs Spring to perform declarative transaction management on annotated classes -->
<tx:annotation-driven />

<!-- Drives transactions using local JPA APIs -->
<bean id="transactionManager" class="org.springframework.orm.jpa.JpaTransactionManager">
<property name="entityManagerFactory" ref="entityManagerFactory" />

<!-- Creates a EntityManagerFactory for use with the Hibernate JPA provider and a simple in-memory data source populated with test data -->
<bean id="entityManagerFactory" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
<property name="dataSource" ref="dataSource" />
<property name="jpaVendorAdapter">
<bean class="org.springframework.orm.jpa.vendor.HibernateJpaVendorAdapter" />

<!-- Deploys a in-memory "booking" datasource populated -->
<bean id="dataSource" class="org.springframework.jdbc.datasource.DriverManagerDataSource">
<property name="driverClassName" value="org.hsqldb.jdbcDriver" />
<property name="url" value="jdbc:hsqldb:mem:booking" />
<property name="username" value="sa" />
<property name="password" value="" />

h3. Resources

[Spring Web Flow 2.5 Documentation||Spring Web Flow 2.5 Documentation]