IBM Support

PH40302: ECLIPSELINK BEHAVIOR CHANGE FOR BOOLEAN VALUES IN CASE SELECT EXPRESSIONS

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

  • Starting in WebSphere release 9.0.5.7, EclipseLink changed
    behavior for CASE select expressions. EclipseLink now returns
    boolean type values instead of integer type values for CASE
    select expressions.
    
    This causes existing applications to fail at runtime with an
    unexpected query return type if they are coded to expect
    Integer types.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server - Java Persistence API - JPA 2.1 &   *
    *                  EclipseLink                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: JPA CASE expressions return type        *
    *                      change in behavior.                     *
    *                      This is a regression fix for PH30837.   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    APAR PH30837 delivered a change in behavior for CASE
    expressions in EclipseLink. With APAR PH30837, EclipseLink
    started converting query return types of INTEGER to BOOLEAN if
    the JPQL expected BOOLEAN. However, that change in behavior
    was supposed to be guarded by a persistence property
    "eclipselink.allow-result-type-conversion" for JPA Container
    managed persistence. This APAR now correctly applies
    this persistence property in order to preserve original
    behavior.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PH40302

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-09-01

  • Closed date

    2021-11-17

  • Last modified date

    2021-11-17

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0"}]

Document Information

Modified date:
18 November 2021