Initial work on the integration allows delegation of the JSF lifecycle to the Spring Web Flow Flow Executor. To allow integration with pages not handled by SWF, only those URLs with no "." after the last "/" are delegated, otherwise JSF handles the request directly. The idea is that this should detect those pages that are "extension mapped". (Clearly a better means of detecting which requests should be handled by Spring Web Flow is needed.)
The booking-faces application has been partially ported and checked in. The flow up to "Book Hotel" is functional; the other pages have not been ported (for instance sf: components currently have interoperability problems due to the use of Dojo and the modification of the form submission URL).
swf-booking-jsf under ICEfaces has been improved by catching Spring resource requests in MainServlet, however this does not actually return the requested resource. For that, we need to implement a wrapper for the Spring resource dispatcher or we need to determine how to allow ICEfaces to recover from Spring writing directly to the outputStream when resources are requested during the JSF lifecycle. This is likely the source of the NullPointerException during flush().