[OPENJPA-1599] Cache mode properties passes in to em.find and lock methods are not transient

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0-beta2, 2.0.0-beta3, 2.0.0
• Fix Version/s: 2.0.0
• Component/s: jpa
• Assignee: Albert Lee
• Reporter: Albert Lee
• Created: 25/Mar/10 03:13
• Updated: 22/Apr/10 20:30
• Resolved: 10/Apr/10 21:26

Description

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(); }

}