Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <1515509256.1243015305721.JavaMail.jira@brutus>
Date: Fri, 22 May 2009 11:01:45 -0700 (PDT)
From: "Jody Grassel (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Updated: (OPENJPA-1061) Entities extending from a Mapped
 Superclass that defines the ID fields share the same ObjectID type
 parameter
In-Reply-To: <1239673166.1241548110479.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/OPENJPA-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jody Grassel updated OPENJPA-1061:
----------------------------------

    Attachment:     (was: unitttest.patch)

> 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: Michael Dick
>
> 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.