Description Nobody - feel free to take it 2011-12-06 16:21:44 EST

Build Identifier: 1.0.0

My situation involves updating some legacy code, and enhancing it to make use of javax.persistence annotations for use with Gemini JPA. I'm sure I can solve this issue by improving my @Entity class modelling for this particular class, but my current situation seems to have exposed a problematic case in the internal Gemini codebase which leads to a vague exception.

I have a clumsy @Entity class in my persistence unit which has an excessively complex hierarchy of non-abstract and abstract superclasses.

Various classes in the hierarchy are contributed by different bundles (at least 3 different ones). This could be a red herring, as I have many other working @Entity classes with the same root super class.

The issue takes place every time I call javax.persistence.Persistence.createEntityManagerFactory
and have the offending @Entity class specified in the persistence unit (or when exclude-unlisted-classes=false).

The issue is...
Caused by: java.lang.IndexOutOfBoundsException: Index: 9, Size: 9
	at java.util.ArrayList.rangeCheck(Unknown Source)
	at java.util.ArrayList.get(Unknown Source)
	at org.eclipse.persistence.internal.jpa.metadata.accessors.objects.MetadataAsmFactory.resolveGenericTypes(MetadataAsmFactory.java:151)
	at org.eclipse.persistence.internal.jpa.metadata.accessors.classes.ClassAccessor.resolveGenericTypes(ClassAccessor.java:1611)
	at org.eclipse.persistence.internal.jpa.metadata.accessors.classes.EntityAccessor.discoverMappedSuperclassesAndInheritanceParents(EntityAccessor.java:280)
	at org.eclipse.persistence.internal.jpa.metadata.accessors.classes.EntityAccessor.preProcess(EntityAccessor.java:514)
	at org.eclipse.persistence.internal.jpa.metadata.MetadataProject.processStage1(MetadataProject.java:1590)
	at org.eclipse.persistence.internal.jpa.metadata.MetadataProcessor.processORMMetadata(MetadataProcessor.java:517)
	at org.eclipse.persistence.internal.jpa.deployment.PersistenceUnitProcessor.processORMetadata(PersistenceUnitProcessor.java:526)
	at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.predeploy(EntityManagerSetupImpl.java:1320)
	... 59 more


The code where this takes place looks like:

for (int index = genericTypes.indexOf(parent.getName()) + 1; index < size; index++) {
    String actualTypeArgument = genericTypes.get(index);
    // Ignore extra types on the end of the child, such as
    // interface generics.
    if (parentIndex >= parentGenericTypes.size()) {
        break;
    }
    String variable = parentGenericTypes.get(parentIndex);
    parentIndex = parentIndex + 3;

    // We are building bottom up and need to link up any
    // TypeVariables with the actual class from the originating
    // entity.
    if (actualTypeArgument.length() == 1) {
        index++;
        actualTypeArgument = genericTypes.get(index);
        descriptor.addGenericType(variable, descriptor.getGenericType(actualTypeArgument));
    } else {
        descriptor.addGenericType(variable, actualTypeArgument);
    }
}

Note that the index is incremented (index++) right before the offending call: "genericTypes.get(index)"

Reproducible: Always

Steps to Reproduce:
1. Using gemini.jpa framework....
2. Have an @Entity class with an abstract superclass, where the superclass is non-abstract
3. Request the entityManagerFactory for the persistence unit which contains the class