PK48744: "DUPLICATE COMPONENT" ERRORS ARE RECEIVED WHEN USING JSF.

Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
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: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Receive 'Duplicate component' error when using JSF MYFACES.
  BBOO0220E: SRVE0068E: Uncaught exception thrown in one of the
  service methods of the servlet: /messages/secure/main.jsp.
  Exception thrown : javax.servlet.ServletException: Duplicate
  component ID 'form1:_id3' found in view.
  

Local fix

• To work around the issue simply modify this:
  <hx:inputHelperSetFocus
  target="text561"></hx:inputHelperSetFocus>
  to give it an id, for example:
  <hx:inputHelperSetFocus target="text561"
  id="setFocus"></hx:inputHelperSetFocus>
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of Websphere Application Server    *
  *                 V6.1.0 using Java Server Faces (JSF).        *
  ****************************************************************
  * PROBLEM DESCRIPTION: WebSphere Application Server's JSF      *
  *                      implementation can generate client      *
  *                      identifiers that collide with cached    *
  *                      client identifiers on a post back,      *
  *                      leading to a duplicate client ID        *
  *                      error.                                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  WebSphere Application Server's JSF implementation generates new
  client IDs for some JSF components on a post back.  These new
  IDs can collide with the cached client IDs when the order of
  the components change, or a new component requests an ID that
  did not do so in the previous request.
  

Problem conclusion

• The new custom property com.ibm.ws.jsf.storeDynamicClientIds
  was added. Setting this property to "true" stores the number
  that is used to generate new client IDs in the view between
  requests allowing WebSphere Application Server to avoid
  collisions.
  
  APAR PK48744 requires changes to documentation.
  
  NOTE: Periodically, we refresh the documentation on our
  Web site, so the changes might have been made before you
  read this text. To access the latest on-line
  documentation, go to the product library page at:
  
  http://www.ibm.com/software/webservers/appserv/library
  
  The following changes to the WebSphere Application Server
  Version 6.1. Information Center will be made available.
  
  The topic "Developing Web Applications" will be updated
  to include the following description of the new
  com.ibm.ws.jsf.storeDynamicClientIds custom property:
  
  If you are receiving a duplicate client error when you use the
  JavaServer Faces (JSF) implementation to dynamically add
  components to the tree, it is because the JSF implementation
  generated client identifiers that collide with cached client
  identifiers on a post back. To prevent collision with existing
  client IDs, use the com.ibm.ws.jsf.storeDynamicClientIds
  property to store the number that is used to generate new
  client IDs in the view between requests. The client IDs
  generation process is also modified when this property is set
  to "true".
  
  To prevent collision with existing client IDs, the
  com.ibm.ws.jsf.storeDynamicClientIds property must be set to
  "true" in the web.xml file. For example:
  
  <contex-param>
    <description>If this property is set to true, the number
  that is used to generate new client IDs is stored in the view
  so that it is saved between requests.
    </description>
    <param-name>com.ibm.ws.jsf.storeDynamicClientIds</param-name>
  <param-value>true</param-value>
  </context-param>
  
  APAR PK48744 is currently targeted for inclusion in Service
  Level (Fix Pack) 6.1.0.15 of WebSphere Application Server V6.1
  for z/OS.
  

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:

Modules/Macros

• JSF
  

Fix information

• Fixed component name

  WEBSPHERE FOR Z

• Fixed component ID

  5655I3500

Applicable component levels

• R610 PSY UK33923

     UP08/03/13 P F803

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.