Thanks, Yee and Marco.
Under jsf-spring 2.7.1, here is what I have been using successfully for months:
1) Deleted META-INF/faces-config.xml out of the jsf-spring.jar file
since the file was defective.
2) had variable resolver configured in WEB-INF/faces-config.xml
(restoring functionality from step 1):
<application>
<variable-resolver>de.mindmatters.faces.spring.FacesSpringVariableResolver</variable-resolver>
</application>
3) had request handler filter configured in WEB-INF/web.xml:
<filter>
<filter-name>RequestHandled</filter-name>
<filter-class>de.mindmatters.faces.spring.RequestHandledFilter</filter-class>
</filter>
<filter-mapping>
<filter-name>RequestHandled</filter-name>
<servlet-name>FacesServlet</servlet-name>
</filter-mapping>
4) Had spring listener registered in WEB-INF/web.xml:
<listener>
<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
</listener>
And this all worked great.
Under jsf-spring 3.0.0 M2,
1) There is no META-INF/faces-config.xml file.
2) I have commented out the faces-config.xml variable resolver.
3) I've replaced the RequestHandler class with
de.mindmatters.faces.spring.support.RequestHandledFilter.
4) I've commented out the spring listener.
This generates the following error:
java.lang.IllegalStateException: No FacesSpringWebApplicationContext
found: no FacesSpringContextLoaderListener registered?
The same error is generated if I uncomment the spring listener.
If I use "de.mindmatters.faces.spring.support.ContextLoaderListener"
as the registered listener, I get this error:
java.lang.NoClassDefFoundError: net/sf/cglib/proxy/CallbackFilter
at
de.mindmatters.faces.spring.FacesConfigWebApplicationContext.<init>(FacesConfigWebApplicationContext.java:185)
I'm guessing that a new Code Generation Library
(http://sourceforge.net/projects/cglib) dependency has now be
introduced? I'm not really thrilled about that library becoming part
of my project.
I guess I'll stick with 2.7.1. The upgrade path still seems unclear.
