openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Woods (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-925) Bidirectional OneToOne relation incorrectly set in loadEagerJoin
Date Wed, 18 Feb 2009 15:19:01 GMT

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

Donald Woods commented on OPENJPA-925:
--------------------------------------

Catalina, this looks like like it resolved my testcase for OPENJPA-919, so can we get this
back ported to the 1.2.x branch?
I'll create a patch and attach it, as I need to apply this to my local 1.2.x code and rerun
the failing EJB TCK testcases for Geronimo to verify that this did fix our problems.


> Bidirectional OneToOne relation incorrectly set in loadEagerJoin
> ----------------------------------------------------------------
>
>                 Key: OPENJPA-925
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-925
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 1.2.0, 1.2.1, 1.3.0, 2.0.0-M1, 2.0.0
>            Reporter: Catalina Wei
>            Assignee: Catalina Wei
>
> A test scenario uncovers a bug in eager loading bidirectional OneToOne relation.
>   OneOneParent  has a bidirectional OneToOne relation with OneOneChild as annotated as
following:
> @Entity
> public class OneOneParent {
> ...
>     @OneToOne(mappedBy="parent")
>     private OneOneChild child;
> }
> @Entity
> public class OneOneChild {
> ...
>     @OneToOne
>     private OneOneParent parent;
> }
> Testcase:
> String query = "select c FROM OneOneChild c";
>         Query q = em.createQuery(query);
>         List list = q.getResultList();
>         for (int i = 0; i < list.size(); i++) {
>             OneOneChild c = (OneOneChild) list.get(i);
>             assertEquals(c, c.getParent().getChild());
>         }
> We expect c equals c.getParent().getChild(), but instead got assertion failure.
> It seems to be a bug introduced in performance improvement work (the related issues:
OPENJPA-292 & OPENJPA-744).

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


Mime
View raw message