PH09730: CLASSNOTFOUNDEXCEPTION OCCURRING DURING JSF INITIALIZATION

9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3

APAR status

• Closed as program error.

Error description

• When the jsf-2.2 feature is enabled on 18.0.0.4 -
  application
  initialization is failing because of a
  ClassNotFoundException
  that occurs during JSF initialization.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of JavaServer Faces (JSF) in          *
  *                  WebSphere Application Server version 9.0    *
  *                  as                                          *
  *                  well as users of jsf-2.2 and jsf-2.3 in     *
  *                  WebSphere Liberty.                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: JSF application initialization fails    *
  *                      when a servlet mapping is defined       *
  *                      which                                   *
  *                      cannot be loaded by JSF                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  JSF applications which define a servlet mapping that cannot
  be
  loaded by JSF will fail to initialize. A similar exception
  will
  be seen:
  javax.faces.FacesException:
  java.lang.ClassNotFoundException:
  <classname>
  at
  org.apache.myfaces.shared.util.ClassUtils.simpleClassForName
  (Cla
  ssUtils.java:239)
  at
  org.apache.myfaces.shared.util.ClassUtils.simpleClassForName
  (Cla
  ssUtils.java:215)
  at
  org.apache.myfaces.shared_impl.webapp.webxml.WebXml.getFaces
  Serv
  letMappings(WebXml.java:136)
  at
  org.apache.myfaces.spi.impl.DefaultWebConfigProvider.getFace
  sSer
  vletMappings(DefaultWebConfigProvider.java:46)
  at
  org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces
  (Abs
  tractFacesInitializer.java:161)
  

Problem conclusion

• The JSF MyFaces 2.2 and 2.3 code has been updated to allow
  application initialization to continue as expected in this
  scenario.
  More information about the fix can be found here:
  https://issues.apache.org/jira/browse/MYFACES-4284
  
  The fix for this APAR is currently targeted for inclusion in
  fix
  pack WebSphere Application Server
  9.0.5.1 as well as WebSphere Liberty 19.0.0.4. Please refer
  to
  the Recommended Updates page for delivery
  information:
  http://www.ibm.com/support/docview.wss?
  rs=180&uid=swg27004980
  

Temporary fix

• Set the following web context parameter to "true" to skip
  the
  Faces Servlet mapping check which causes this initialization
  failure:
  org.apache.myfaces.INITIALIZE_ALWAYS_STANDALONE
  

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

  LIBERTY PROFILE

• Fixed component ID

  5724J0814

Applicable component levels

• RCD0 PSY

     UP