[
https://issues.apache.org/jira/browse/OPENJPA-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Bauer updated OPENJPA-1884:
----------------------------------
Attachment: OPENJPA-1884.patch
Attaching fix and updated test code. In addition to handling updates, this fix
also purges entries from the L2 when the property
javax.persistence.cache.storeMode is set to CacheStoreMode.REFRESH and the
refresh operation determines the entity no longer exists in the underlying
datastore/database.
> CacheStoreMode.REFRESH is not recognized for entity manager refresh operation
> -----------------------------------------------------------------------------
>
> Key: OPENJPA-1884
> URL: https://issues.apache.org/jira/browse/OPENJPA-1884
> Project: OpenJPA
> Issue Type: Bug
> Components: datacache
> Affects Versions: 2.1.0
> Reporter: Jeremy Bauer
> Assignee: Jeremy Bauer
> Attachments: OPENJPA-1884-jUnit.patch, OPENJPA-1884.patch
>
>
> Specifying the "javax.persistence.cache.storeMode" property with value
> CacheStoreMode.REFRESH does not refresh the contents of the L2 cache when
> used with the em.refresh(entity, props) operation.
> OPENJPA-1578 corrected this a similar issue for the em.find() operation, but
> not em.refresh(). A simple port of the changes from 1578 (which simply
> configure the store mode in the fetch plan) to the refresh operation did not
> correct the problem. It appears that more work needs to be done in the
> underlying refresh logic to produce a cache refresh.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
