You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/02/28 22:47:12 UTC

[jira] [Commented] (OPENJPA-2305) Canonical MetaModel class generation should not use inhertence

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

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

Commit 1451369 from [~ppoddar@apache.org]
[ https://svn.apache.org/r1451369 ]

OPENJPA-2305: Restore the inheritance hierarchy of the generated canonical metamodel to that of the domain model due to spec compliance, but flatten the attributes so that an inherited attribute uses generic parameter of owning class type instead of the declared supertype
                
> Canonical MetaModel class generation should not use inhertence
> --------------------------------------------------------------
>
>                 Key: OPENJPA-2305
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2305
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: criteria
>    Affects Versions: 2.2.1.1
>            Reporter: Pinaki Poddar
>            Assignee: Pinaki Poddar
>             Fix For: 2.2.1.1
>
>
> The generated source code for canonical metamodel classes mirrored the same inheritance hierarchy of the domain classes. This strategy exposed an error that resulted in wrong target SQL query under the following domain model 
> a) A @MappedSuperClass M defined a primary key field x
> b) The primary key field x is an @EmbeddedId E
> c) An @Entity class D derived from M and navigated to the fields of E via x
> The solution is to generate canonical class D_.java as a flattened structure instead of inheriting from M_.java (as is done currently). 

--
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