openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Curtis (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OPENJPA-1767) OneToMany relationships owned by the many side aren't properly evicted from the DataCache
Date Fri, 13 Aug 2010 19:44:15 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rick Curtis updated OPENJPA-1767:
---------------------------------

    Description: 
When working on OPENJPA-1469 I found that the test org.apache.openjpa.persistence.spring.TestLibService
fails because we have stale data in the cache.  To recreate this failure, set "openjpa.DataCache","true"
in the setup() method.

The net of the problem is that if the non-owning side of the relationship exists in the datacache
and the relationship is updated on the owning side, the non-owning side doesn't get updated.



  was:
When working on OPENJPA-589 I found that the test org.apache.openjpa.persistence.spring.TestLibService
fails because we have stale data in the cache.  To recreate this failure, set "openjpa.DataCache","true"
in the setup() method.

The net of the problem is that if the non-owning side of the relationship exists in the datacache
and the relationship is updated on the owning side, the non-owning side doesn't get updated.




Updated desc to reference proper JIRA.

> OneToMany relationships owned by the many side aren't properly evicted from the DataCache
> -----------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-1767
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1767
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: datacache
>    Affects Versions: 2.0.0, 2.1.0
>            Reporter: Rick Curtis
>            Priority: Critical
>
> When working on OPENJPA-1469 I found that the test org.apache.openjpa.persistence.spring.TestLibService
fails because we have stale data in the cache.  To recreate this failure, set "openjpa.DataCache","true"
in the setup() method.
> The net of the problem is that if the non-owning side of the relationship exists in the
datacache and the relationship is updated on the owning side, the non-owning side doesn't
get updated.

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