Change checked in for ICE-6791 should resolve response staleness.

Stale responses are no longer present during user interaction, but are present during Ajax Push. The proposed technique to resolve will be as follows:

Create a Servlet Filter to inject a FailSafeResponseWrapper. This must be in the Filter chain prior to the Seam Filters. The FailSafeResponseWrapper will allow encode*() to proceed using the Seam wrapper on the stale HttpServletResponse.

The attached FailSafeResponseFilter wraps the Response in a version that does not throw an Exception when it has gone out of request processing scope. It must be added to the web.xml prior to the Seam Filter:

<filter>
<filter-name>FailSafe</filter-name>
<filter-class>FailSafeResponseFilter</filter-class>
</filter>

<filter-mapping>
<filter-name>FailSafe</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>

Since the specific failure seen by the customer has not been reproduced in the test application, the FailSafeResponseFilter contains substantial System.out output and is implemented in the default package so that it can be compiled directly within the "classes" directory or added to an existing project at the root level.

Updated to include FailSafeRequestWrapper.

Configured via:

<filter>
<filter-name>FailSafe</filter-name>
<filter-class>com.icesoft.faces.webapp.http.servlet.FailSafeResponseFilter</filter-class>
</filter>

<filter-mapping>
<filter-name>FailSafe</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>