Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <19476566.1187958815623.JavaMail.jira@brutus>
Date: Fri, 24 Aug 2007 05:33:35 -0700 (PDT)
From: "Ekin Sokmen (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Updated: (OPENJPA-334) ManyToMany relationship not handled
 properly while using QueryCache .
In-Reply-To: <27222156.1187958814327.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-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ekin Sokmen updated OPENJPA-334:
--------------------------------

    Attachment: testcase_querycache.zip

Testcase demonstrating the QueryCache problem

> ManyToMany relationship not handled properly while using QueryCache .
> ---------------------------------------------------------------------
>
>                 Key: OPENJPA-334
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-334
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: datacache
>    Affects Versions: 1.0.0
>         Environment: Fedora 6
> Java 1.5.0_11
>            Reporter: Ekin Sokmen
>         Attachments: testcase_querycache.zip
>
>
> Following description is a simplified model of the issue we are facing. 
> Assume that we have 2 entities EntityA and EntityB in ManyToMany relationship. We are going to create a new instance of EntityA and add an existing instance of EntityB to it. We are creating a new POJO instance of EntityA and add an existing instance of EntityB to it. Then we persists the new instance of EntityA. Then we retrieve the instance of EntityA using OpenJPA and check the content of it. Without QueryCache this works well. But if the query cache is enabled the first time we get the instance of EntityA we get a properly populated EntityA instance but the second time we try to retrieve the same instance we get an empty set of included EntityB instance(s).
> The attached test case demonstrates this issue clearly.

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