PM16904: PERSONALIZATION COMPONENT USING A BINDING RULE IS NOT WORKING IN WCM

APAR status

• Closed as program error.

Error description

• PERSONALIZATION COMPONENT USING A BINDING RULE IS NOT WORKING
  IN WCM
  
  Steps to recreate the issue.
  
  1.Create a binding rule in the personalization, containing
  three action rules.
  2.The action rules refer to a html component.
  3.In Personalization preview you would see correct
  results.
  4.Using the binding rule in a personalization component
  used in a Presentation template shows no results.
  

Local fix

Problem summary

• Problem Summary:
  NPE PERSONALIZATION COMPONENT USING A BINDING RULE IS NOT
  WORKING IN WCM
  
  Detailed Problem Description:
  When attempting to use a PZN Binding Rule in a WCM
  personalization component a NullPointerException is thrown.
  [4/30/10 11:13:07:568 CEST] 0000004f Personalizati 3
  com.ibm.websphere.personalization.context.PersonalizationContext
  getApplicationObject Could not initialize applicaton object
                                   java.lang.NullPointerException
     at com.ibm.workplace.wcm.pzn.resources.WcmContentResource
  .init(WcmContentResource.java:511)
     at com.ibm.websphere.personalization.context
  .PersonalizationContext.getApplicationObject(PersonalizationCont
  ext.java:291)
     at com.ibm.websphere.personalization.rules.PznXMLInterpreter
  .getContextObject(PznXMLInterpreter.java:988) . . .
  In this case the customer was using the current content to
  determine the value returned.
  

Problem conclusion

• Problem Analysis:
  This happens because WcmContentResource.init is attempting to
  get the RenderContext using the request attributes but the
  RenderContext was not added by WCM.  Therefore, when
  personalization attempts to get the content from the
  RenderContext a NPE results.
  
  Problem Solution:
  Updated the WCM code to add the RenderContext so PZN can
  determine the current content.
  
  Affected Users:
  Users of personalization components that reference binding
  rules.
  

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

  LOTUS WEB CONT

• Fixed component ID

  5724I2900

Applicable component levels

• R610 PSY

     UP

• R61A PSY

     UP

• R61B PSY

     UP

• R61C PSY

     UP

• R610 PSY

     UP

• R615 PSY

     UP