Details
Description
When a mapped superclass (MSC) defines @Id fields, it appears that entities extending the MSC use the MSC's type in the generated ObjectID's type field. This can result in unexpected primary key collissions between entities that are not intended to be related in an entity inheritance hierarchy. Attached to the JIRA is a junit test case that demonstrates the problem.
Attachments
Issue Links
- incorporates
-
OPENJPA-1156 Path length issues on Windows
- Closed