Simple JSF ScopeFlow is initially developed with JSF 1.2 Mojarra and Spring Web 2.5.x. For JSF, only the PAI is used so there should be no problem of running the Simple JSF FlowScope on any 1.2 compliant implementation of JSF (Mojarra or myFaces). From Spring, we used the SpringBeanFacesELResolver which is available frmo the 2.5 onwards. Both dependencies are set to the compile scope in the POM so that the integration into an application should be very easy. As long as the project contains a JSF 1.2 compliant implementation and Spring 2.5 or higher, things should be working.
Since Simple JSF ScopeFlow has such a 'simple' concept, we tried to port it to JSF 1.1. There was only a small issue that took a bit of time to solve and the requirement of a new VariableResolver. The DelegatingVariableResolver of Spring looks first in the original resolver (JSF in our case) and then in the application context of Spring if no bean could be found. Since we use the session to store the beans defined in the custom scope sfs , the JSF resolver is able to find the bean the second time we ask for it. But since our custom scope is not called, the bean is not marked as used and the JSF PhaseListener removed from the session. So we made our variableResolver where we used the same code as Spring does. But the SFSDelegatingVariableResolver looks first into the Spring application context and then in the JSF Managed Bean facility.