Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 1.8.2-EE-GA
-
Fix Version/s: 1.8.2-EE-GA_P01, 1.8.3
-
Component/s: Framework
-
Labels:None
-
Environment:ICEfaces, no spring web flow
Description
Now that we are not caching the SWF Executor, it appears that an attempt is made to invoke SWF even when it is not present.
[#|2010-01-25T11:39:02.429-0700|SEVERE|glassfishv3.0|com.icesoft.faces.context.View|_ThreadID=25;_ThreadName=Thread-1;|Problem encountered during View.servePage
java.lang.NoClassDefFoundError: org/springframework/webflow/context/ExternalContext
at com.icesoft.faces.webapp.http.core.LifecycleExecutor.getLifecycleExecutor(LifecycleExecutor.java:17)
at com.icesoft.faces.context.View$2$1.respond(View.java:48)
at com.icesoft.faces.webapp.http.servlet.ServletRequestResponse.respondWith(ServletRequestResponse.java:201)
at com.icesoft.faces.context.View$2.serve(View.java:82)
at com.icesoft.faces.context.View.servePage(View.java:154)
at com.icesoft.faces.webapp.http.core.SingleViewServer.service(SingleViewServer.java:52)
at com.icesoft.faces.webapp.http.common.ServerProxy.service(ServerProxy.java:11)
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
If SWF is suspected (based on no path mapping) but fails during instantiation, a key will be placed in the application map. If the key is present, the standard JSF lifecycle will be used.