[
https://issues.apache.org/jira/browse/OPENJPA-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods resolved OPENJPA-1599.
-----------------------------------
Resolution: Fixed
Code checked into 2.0.0, so marking it resolved for the release notes.
If more work is required, please open a new issue and link it to this one.
> Cache mode properties passes in to em.find and lock methods are not transient
> -----------------------------------------------------------------------------
>
> Key: OPENJPA-1599
> URL: https://issues.apache.org/jira/browse/OPENJPA-1599
> Project: OpenJPA
> Issue Type: Bug
> Components: jpa
> Affects Versions: 2.0.0-beta2, 2.0.0-beta3, 2.0.0
> Reporter: Albert Lee
> Assignee: Albert Lee
> Fix For: 2.0.0
>
>
> Cache mode properties passes in to em.find and lock methods are not transient
> and permanently
> set to the entity manager, which caused subsequent em operations to use the
> undesired
> cache mode.
> public <T> T find(Class<T> cls, Object oid, LockModeType mode,
> Map<String, Object> properties) {
> assertNotCloseInvoked();
> configureCurrentCacheModes(getFetchPlan(), properties); <<----
> pushFetchPlan call should be performed first before the getFetchPlan
> configureCurrentFetchPlan(pushFetchPlan(), properties, mode, true);
> try {
> oid = _broker.newObjectId(cls, oid);
> return (T) _broker.find(oid, true, this);
> } finally {
> popFetchPlan();
> }
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
