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

8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2

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 is sysrouted FROM one or more of the following:

  PM66740

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

Fix information

• Fixed component name

  LIBERTY PROFILE

• Fixed component ID

  5724J0814

Applicable component levels

• R850 PSY

     UP