IBM Support

PQ99195: MANAGED BEAN IS NOT BEING INITIALIZED IN RAD V6

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Managed bean is not being initialized when in application scope
    while running on the WebSphere Application server.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: WebSphere Application Server users of        *
    *                 JavaServer Faces (JSF).                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: JSF managed bean is not set             *
    *                      properly when bean property value       *
    *                      is associated with another managed      *
    *                      bean.                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When the JSF container is parsing the applications-managed
    beans for the application, the container is not properly
    updating the list of managed beans handled by the
    JSF ManagedBeanFactory.  When the JSF runtime attempts to
    resolve the property #{mgBean1} that is associated with the
    managed bean "userBean", the following message is
    logged (if trace was enabled):
    
    "com.sun.faces.config.ManagedBeanFactory
    getManagedBeanFactoryMap Contract violation:
    ManagedBeanFactory must be initialized with
    managedBeanFactoryMap after instantiation"
    and resulted in the following exception:
    javax.faces.el.PropertyNotFoundException : Can't set
    managed bean property <xyz>"
    
    sample snippet of faces-config.xml demonstrating problem:
    
    #### begin  ########
    
    <managed-bean>
     <managed-bean-name>mgBean1</managed-bean-name>
     <managed-bean-class>com.someco.MyClass</managed-bean-class>
     <managed-bean-scope>application</managed-bean-scope>
    </managed-bean>
    <managed-bean>
     <managed-bean-name>userBean</managed-bean-name>
     <managed-bean-class>com.someco.MyUser</managed-bean-class>
     <managed-bean-scope>session</managed-bean-scope>
     <managed-property>
     <property-name>specialProp</property-name>
        <value>#{mgBean1}</value>
     </managed-property>
    </managed-bean>
    
    #### end ########
    

Problem conclusion

  • Modified the JSF container to properly update the map
    containing all managed beans handled by the
    ManagedBeanFactory.
    
    The fix for this APAR is currently targeted for inclusion in
    6.0.0.2.  Refer to the Recommended Updates page for
    delivery dates:
    
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PQ99195

  • Reported component name

    WEBSPH APP SERV

  • Reported component ID

    5724J0800

  • Reported release

    60W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2005-01-07

  • Closed date

    2005-01-11

  • Last modified date

    2007-03-01

  • 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

Applicable component levels

  • R60A PSY

       UP

  • R60H PSY

       UP

  • R60I PSY

       UP

  • R60P PSY

       UP

  • R60S PSY

       UP

  • R60W PSY

       UP

  • R60Z PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCVS22","label":"General"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 March 2007