openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OPENJPA-2325) MappedSuperClass without an @Id causes wrong identity type for the inherited types
Date Thu, 18 Apr 2013 21:28:15 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635715#comment-13635715
] 

ASF subversion and git services commented on OPENJPA-2325:
----------------------------------------------------------

Commit 1469582 from hthomann
[ https://svn.apache.org/r1469582 ]

OPENJPA-2325: MappedSuperClass without an @Id causes wrong identity type for the inherited
types - back-ported to 2.0.x Pinaki Poddar's commit to trunk, as well as an additional change
he made specific to 2.0.x.
                
> MappedSuperClass without an @Id causes wrong identity type for the inherited types
> ----------------------------------------------------------------------------------
>
>                 Key: OPENJPA-2325
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2325
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 2.3.0
>            Reporter: Pinaki Poddar
>            Assignee: Pinaki Poddar
>             Fix For: 2.3.0
>
>
> A MappedSuperClass without a declared identity field can cause the derived classes that
have decalred an @Id field to be wrongly using DATASTORE identity type because the identity
type of its superclass being UNKNOWN leads the derived type to use the default identity type,
which for JPA faced is set to DATASTORE. 
> The suggested change modifies the logic of ClassMetaData while detecting the identity
type whether it is an abstract (i.e. MappedSuperClass). Also introduced a change that distinguishes
whether the identity type was ever evaluated versus whether identity type  is indeterminable
(i.e. UNKNOWN) which will  will save few  cycles for this commonly invoked operation. Previously
for UNKNOWN type was indistinguishable from the case where identity type was never evaluated.
  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message