IBM Support

PM66740: EJB 3.0 CLASSCASTEXCEPTION WITH CODE TABLE WHEN USING AN ORM.XML

Fixes are available

7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The stack will contain
    
    java.lang.ClassCastException: java.lang.Object; incompatible
    with test.servlet.CodeTable
    
    when attempting to call a Stored Procedure using JPA and cast
    the resulting data to the appropriate class.
    

Local fix

  • Move the the orm.xml contents to annotations on the class.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0.0, V8.0.0, and V8.5.0 who make  *
    *                  use of column names with number values in   *
    *                  their Java Persistence API (JPA) Entities.  *
    ****************************************************************
    * PROBLEM DESCRIPTION: Incorrectly generated SQL for numeric   *
    *                      column names defined in JPA Entities.   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a numeric column name is specified with a single number
    (for example: "1"), incorrect SQL is generated. The SQL is
    supposed to have a single set of double quotes around the name.
    Different incorrect SQL is generated, depending on the OpenJPA
    release.  For JPA 1.0 releases of OpenJPA, there are no quotes
    (for example: 1). For JPA 2.0 releases of OpenJPA, there are 2
    sets of double quotes (for example: ""1"").  To follow are some
    examples for databases that support double quote delimiters:
    *For annotations:
    @Column(name = "\"2\"")
     ‚   ‚   ‚   ‚  public String description;
    *For xml:
     &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160;<attributes>
    <id name="id">
    <column name="&quot;1&quot;" />
    </id>
    <basic name="description">
    <column name="&quot;2&quot;" />
    </basic>
    </attributes>
    With this example in mind, and given this issue is slightly
    different on the different OpenJPA releases, we must describe
    the issue as it relates to the various JPA releases of
    OpenJPA, as follows:
    *For JPA 1.0 releases of OpenJPA, a column name that starts
    with a number doesn't work and as mentioned incorrect SQL is
    generated.  The column name needs to be delimited with the the
    specific database delimiter in the SQL. However, delimited
    identifiers are not supported in the JPA specification until
    JPA 2.0.  OpenJPA does however attempt to support delimited
    identifies to a certain point in JPA 1.0 releases.  Even
    manually delimiting the column name in the annotation or orm
    xml causes a problem.  Note that this APAR only address and
    fixes column names.  Manual delimiting of other database
    identifiers may not work on JPA 1.0 releases of OpenJPA.
    *For JPA 2.0 release of OpenJPA, delimited identifier support
    is mandated by the JPA 2.0 specification and is provided in the
    corresponding OpenJPA releases.  This provides support for
    both manually delimited identifiers and auto delimiting
    identifiers based on 'starting' and 'embedded' characters.
    However, there is a simple bug in this support when a single
    numeric name is provided as a column name (as mentioned above,
    incorrect SQL is generated).
    

Problem conclusion

  • This fix will allow proper SQL to be generated for manually
    delimiting column names in JPA 1.0 releases of OpenJPA.  On
    JPA 2.0 release of OpenJPA, this fix will allow proper SQL to
    be generated for both manually delimited identifiers and auto
    delimiting identifiers.
    
    The fix for this APAR is currently targeted for
    inclusion in Service Levels (Fix Packs) 7.0.0.25, 8.0.0.5, and
    8.5.0.1 of WebSphere Application Server versions 7.0.0, 8.0.0,
    and 8.5.0.
    
    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

    PM66740

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-06-13

  • Closed date

    2012-07-09

  • Last modified date

    2012-07-13

  • APAR is sysrouted FROM one or more of the following:

    PM64160

  • APAR is sysrouted TO one or more of the following:

    PM70230

Fix information

  • Fixed component name

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM66740

Modified date: 13 July 2012