PM25223: FAILED TO INCLUDE A JSF PAGE WITHIN THE SERVLET.

6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• Within a servlet when a Servlet context of the Faces application
  is obtained and then used to include a JSF page it fails to
  run the page.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server Version    *
  *                  6.1 users of JavaServer Faces (JSF).        *
  ****************************************************************
  * PROBLEM DESCRIPTION: JSF resources which are requested as    *
  *                      an include might not receive a          *
  *                      mapping to the Faces servlet.           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If the JSF resource is an include, the appropriate Faces
  mapping might not be found when determining the Faces mapping
  which matches the JSF request.  This can be typical in a
  Portal Server environment.  The issue typically occurs on
  applications which were written based on the behavior in JSF
  1.0, which is included in WebSphere Application Server version
  6.0.2.
  If the Faces mapping is not found for such a request, the JSF
  code will complete the response and redirect the request to
  the context root of the application.
  

Problem conclusion

• The JSF code was modified to allow the behavior in JSF 1.0 to
  be used in JSF 1.1.  This behavior will allow JSF to use the
  default mapping for these JSF requests.  To enable this
  behavior, the following context parameter must be set to true
  in the application's web.xml file:
  
  com.ibm.ws.jsf.enable10Mapping
  
  An example entry is:
  
  <context-param>
  <param-name>com.ibm.ws.jsf.enable10Mapping</param-name>
  <param-value>true</param-value>
  </context-param>
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 6.1.0.39.  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 is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP