IBM Support

PI70861: The jsf-2.0 and jsf-2.2 features have org.apache.commons.logging exposed as API

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • The jsf-2.0 and jsf-2.2 features incorrectly export the
    org.apache.commons.logging package as API and should not.
    This means that customers who have one of these two features
    enabled can not use their own commons logging
    implementation.
    
    There are some issues caused by this, mainly it conflicts
    with a user provided version in an application.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server Liberty    *
    *                  Profile users of JavaServer Faces (JSF)     *
    *                  MyFaces 2.0 and 2.2                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: The JSF features expose the apache      *
    *                      commons-logging package as API          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Currently the JSF 2.0 and JSF 2.2 features incorrectly export
    the org.apache.commons.logging package as API. As a result,
    customers can not use their own commons logging implementation
    if they have one of these two features enabled.
    

Problem conclusion

  • The JSF 2.0 and JSF 2.2 features were updated to not expose the
    apache commons-logging package as API. From now on, the apache
    commons-logging library needs to be included as part of the
    application.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 16.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

Comments

APAR Information

  • APAR number

    PI70861

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-10-18

  • Closed date

    2016-10-25

  • Last modified date

    2016-10-25

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"CD0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2016