anchor.diff:  The filter is what is in charge of replacing the `HttpSession` implementation to be backed by Spring Session.
   In this instance Spring Session is backed by Redis.
   <3> We create a `RedisConnectionFactory` that connects Spring Session to the Redis Server.
  -In our example, we are connecting to localhost on the default port (6379).
  +We use a http://docs.spring.io/spring/docs/current/spring-framework-reference/htmlsingle/#xsd-config-body-schemas-context-pphc[PropertyPlaceholderConfigurer] to externalize the port location.
   For more information on configuring Spring Data Redis, refer to the http://docs.spring.io/spring-data/data-redis/docs/current/reference/html/[reference documentation].
   
  -== Servlet Container Initialization
  +== Java Servlet Container Initialization
   
   Our <<httpsession-spring-configuration,Spring Configuration>> created a Spring Bean named `springSessionRepositoryFilter` that implements `Filter`.
   The `springSessionRepositoryFilter` bean is responsible for replacing the `HttpSession` with a custom implementation that is backed by Spring Session.
  
positive.code: 
  Try using the application. Fill out the form with the following information:
  
  * **Attribute Name** *username*
  * **Attribute Value** *rob*
  
  Now click the **Set Attribute** button. You should now see the values displayed in the table.
  
  
negative.code: Rob Winch
  :toc:
  
  This guide describes how to use Spring Session to transparently leverage Redis to back a web application's `HttpSession` with Java Configuration.
  
  NOTE: The completed guide can be found in the <<httpsession-sample, httpsession sample application>>.
  
  