Use of @Embeddable class causes an unexpected index out of bounds before request is sent to the database. Given the follow scenario, a simple list() call was made to retrieve all entries.
The following exception occurs before a call is made to the database
The stack trace references the following code within Hibernate. When debugging, it was found it is invoked for each field of the Address Embeddable.
In this segment of code, propertyNumber is defined to be the position of the field within the Address Embeddable. In the above Address example, this could be a value from 0 through 3. Then tableNumber is retrieved using getSubclassPropertyTableNumber which defines only two entries, being the table reference for the Person and Address objects. The bug seems to be using the position of the Embeddable field to retrieve the tab reference for the entity. When the number of fields in the embeddable exceeds the number of Embeddable entries in the parent object, the observed index out of bounds exception occurs. |