Fixes are available
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
APAR status
Closed as program error.
Error description
When using the Annotation type @ConversationScpoed customer is getting a FacesException.
Local fix
Setting the JSF Project Stage to "Production" in the web.xml and redeploying the application resolves
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server Version * * 8.0 users of MyFaces JavaServer Faces * * (JSF). * **************************************************************** * PROBLEM DESCRIPTION: When using the MyFaces implementation * * JSF 2.0 and Contexts and Dependency * * Injection (CDI) an exception occurs * * when a @ConversationScoped parameter * * is used in a Transient Conversation * **************************************************************** * RECOMMENDATION: * **************************************************************** If the JSF Project Stage is set to "Development" the following exception can occur: javax.faces.FacesException: javax.enterprise.context.ContextNotActiveException: WebBeans context with scope type annotation @ConversationScoped does not exist within current thread at org.apache.myfaces.shared_impl.context.ExceptionHandlerImpl.wrap ExceptionHandlerImpl.java:241) at org.apache.myfaces.shared_impl.context.ExceptionHandlerImpl.hand le(Excep tionHandlerImpl.java:156) This error occurs because MyFaces has a DebugPhaseListener that is executed before the CDI PhaseListener that sets the ConversationScope to active. The DebugPhaseListener is attempting to resolve all of the Expression Language expressions which is what leads to the ContextNotActiveException.
Problem conclusion
The following MyFaces bug was pulled into WebSphere Application Server: https://issues.apache.org/jira/browse/MYFACES-3187\\ The following JSF context parameter can be set to true: org.apache.myfaces.DEBUG_PHASE_LISTENER (default false) to enable the DebugPhaseListener in the Development Project Stage. The fix for this APAR is currently targeted for inclusion in fix pack 8.0.0.3. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM52695
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-11-21
Closed date
2012-01-06
Last modified date
2012-03-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R800 PSY
UP
Document Information
Modified date:
28 October 2021