You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Rick McGuire (JIRA)" <ji...@apache.org> on 2008/07/18 14:58:33 UTC

[jira] Created: (OPENEJB-860) CMP 1.x beans with complex keys can generate an incorrect JPA mapping.

CMP 1.x beans with complex keys can generate an incorrect JPA mapping. 
-----------------------------------------------------------------------

                 Key: OPENEJB-860
                 URL: https://issues.apache.org/jira/browse/OPENEJB-860
             Project: OpenEJB
          Issue Type: Bug
          Components: cmp2
            Reporter: Rick McGuire
            Assignee: Rick McGuire
            Priority: Minor


The code that generates the JPA mapped superclasses for CMP 1.x entity beans can create an incorrect mapping if the beans use complex keys and the key fields are implemented on different subclasses of the hierarchy.  In this situation, one of the subclasses is identified as the idClass().  If the subclass chosen happens to be the most-derived type, then the mapping will be correct.   Any other choice will generate an incorrect mapping.  This code needs to ensure that the most-derived type gets marked.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (OPENEJB-860) CMP 1.x beans with complex keys can generate an incorrect JPA mapping.

Posted by "Rick McGuire (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OPENEJB-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick McGuire resolved OPENEJB-860.
----------------------------------

    Resolution: Fixed

Committed revision 677894.

> CMP 1.x beans with complex keys can generate an incorrect JPA mapping. 
> -----------------------------------------------------------------------
>
>                 Key: OPENEJB-860
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-860
>             Project: OpenEJB
>          Issue Type: Bug
>          Components: cmp2
>            Reporter: Rick McGuire
>            Assignee: Rick McGuire
>            Priority: Minor
>
> The code that generates the JPA mapped superclasses for CMP 1.x entity beans can create an incorrect mapping if the beans use complex keys and the key fields are implemented on different subclasses of the hierarchy.  In this situation, one of the subclasses is identified as the idClass().  If the subclass chosen happens to be the most-derived type, then the mapping will be correct.   Any other choice will generate an incorrect mapping.  This code needs to ensure that the most-derived type gets marked.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (OPENEJB-860) CMP 1.x beans with complex keys can generate an incorrect JPA mapping.

Posted by "David Blevins (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OPENEJB-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Blevins updated OPENEJB-860:
----------------------------------

        Fix Version/s: (not version related)
    Affects Version/s: (trunk/openejb3)

> CMP 1.x beans with complex keys can generate an incorrect JPA mapping. 
> -----------------------------------------------------------------------
>
>                 Key: OPENEJB-860
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-860
>             Project: OpenEJB
>          Issue Type: Bug
>          Components: cmp2
>    Affects Versions: (trunk/openejb3)
>            Reporter: Rick McGuire
>            Assignee: Rick McGuire
>            Priority: Minor
>             Fix For: (not version related)
>
>
> The code that generates the JPA mapped superclasses for CMP 1.x entity beans can create an incorrect mapping if the beans use complex keys and the key fields are implemented on different subclasses of the hierarchy.  In this situation, one of the subclasses is identified as the idClass().  If the subclass chosen happens to be the most-derived type, then the mapping will be correct.   Any other choice will generate an incorrect mapping.  This code needs to ensure that the most-derived type gets marked.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.