[OPENJPA-386] org.apache.openjpa.meta.ClassMetaData.validateAppIdClass() does not take @MappedSuperclass into account

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.9.7, 1.0.0, 1.0.2, 1.1.0, 1.2.1
• Fix Version/s: 1.2.0, 1.3.0, 2.0.0-M3
• Component/s: kernel
• Environment: BEA WebLogic 10.0 under Windows XP SP1
• Patch Info: Patch Available
• Assignee: Jody Grassel
• Reporter: Matthew L. Schwickerath
• Created: 27/Sep/07 14:26
• Updated: 21/Sep/16 14:21
• Resolved: 27/Aug/09 20:07

Description

We have a @MappedSuperclass that is the base for all of our entity bean classes. This class contains the @Version (and @Column for the version field) that all of our entity beans use. But, in ClassMetaData.validateAppIdClass(), if an entity bean class has a superclass, and the entity bean has an @IdClass, it expects that superclass to have an @IdClass also. All of our entity beans have an @IdClass (even if they only have a single part key), but our @MappedSuperclass does not have an @IdClass. This scenario works under JBoss 4.2.0 and Sun AS 9, but produces a NullPointerException in OpenJPA at:

if (_super != null) {
// concrete superclass oids must match or be parent of ours
ClassMetaData sup = getPCSuperclassMetaData();
if (!sup.getObjectIdType().isAssignableFrom(_objectId)) // <--- NullPointerException here