[
https://issues.apache.org/jira/browse/OPENJPA-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706264#action_12706264
]
Pinaki Poddar commented on OPENJPA-1061:
----------------------------------------
I have added a new method ClassMetaData.isAbstract() which affirms (in JPA
context) for MappedSuperclass. This method may help to identify whether a type
is MSC.
> Entities extending from a Mapped Superclass that defines the ID fields share
> the same ObjectID type parameter
> -------------------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-1061
> URL: https://issues.apache.org/jira/browse/OPENJPA-1061
> Project: OpenJPA
> Issue Type: Bug
> Components: jpa
> Affects Versions: 1.2.0, 1.2.1
> Reporter: Jody Grassel
> Assignee: Jody Grassel
> Attachments: PCEnhancer.patch, unitttest.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
