PM24390: WARNING MESSAGES FROM JAVASERVER FACES COMPONENT FILSYSTEMOUT.LOG

6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
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

• When a JavaServer Faces (JSF) configuration file contains
  non-standard elements, then the following warning message is
  filled in SystemOut.log file:
  0000001c jsf           W
  com.ibm.ws.jsf.configuration.FacesConfigParser parseShared
  FacesConfigParser.parseShared(): unable to locate : [XXXXXXXX]
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server Version    *
  *                  6.1 users of the JavaServer Faces           *
  *                  (JSF) Sun reference  implementation         *
  *                  (SunRI).                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: Many warning messages from the JSF      *
  *                      configuration file parser are logged    *
  *                      to the SystemOut.log file when          *
  *                      third-party JSF libraries are used.     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Third-party JSF libraries, such as Trinidad, can contain
  elements in their faces-config.xml file which are not
  considered standard to JSF.  During the parsing of the
  faces-config.xml files, the JSF configuration parser code will
  log a warning message for elements which are not recognized.
  
  For example, the following Warning messages are logged:
  
  W com.ibm.ws.jsf.configuration.FacesConfigParser parseShared
  FacesConfigParser.parseShared(): unable to locate :
  [property-metadata]
  W com.ibm.ws.jsf.configuration.FacesConfigParser parseShared
  FacesConfigParser.parseShared(): unable to locate :
  [component-metadata]
  W com.ibm.ws.jsf.configuration.FacesConfigParser parseShared
  FacesConfigParser.parseShared(): unable to locate : [group]
  

Problem conclusion

• The JSF code was modified to allow you to set a context
  parameter which will change the warning messages to trace
  statements.  Therefore, if tracing is not enabled the warning
  messages will be suppressed.
  To enable this behavior the following context parameter must
  be set to true in the application's web.xml file:
  com.ibm.ws.jsf.ignoreAdditionalElements
  An example entry in the web.xml file is:
  
  <context-param>
  <param-name>com.ibm.ws.jsf.ignoreAdditionalElements</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.37.  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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP