[
https://issues.apache.org/jira/browse/OPENJPA-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15670547#comment-15670547
]
Yves De Moor commented on OPENJPA-2679:
---------------------------------------
The workaround / consequence is to define the version field in all sub-classes
instead of in the super class.
> Version field in a mapped super class causes
> java.lang.ArrayIndexOutOfBoundsException
> -------------------------------------------------------------------------------------
>
> Key: OPENJPA-2679
> URL: https://issues.apache.org/jira/browse/OPENJPA-2679
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 1.2.3, 1.3.0
> Reporter: Yves De Moor
> Labels: easyfix
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Version field in a mapped super class causes
> java.lang.ArrayIndexOutOfBoundsException
> StackTrace version 1.2.3
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 0
> at
> org.apache.openjpa.jdbc.sql.DBDictionary.appendUpdates(DBDictionary.java:2124)
> at
> org.apache.openjpa.jdbc.sql.DBDictionary.toBulkOperation(DBDictionary.java:2068)
> at
> org.apache.openjpa.jdbc.sql.DBDictionary.toUpdate(DBDictionary.java:1953)
> The bug has been fixed in 2.x version, in class
> org.apache.openjpa.jdbc.meta.FieldMapping, in method public Column[]
> getColumns() by rgc : 2 March 2011
> The idea is to backport this method from 2.4.0 to 1.x
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
