You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Donald Woods (JIRA)" <ji...@apache.org> on 2009/10/30 19:04:59 UTC
[jira] Resolved: (OPENJPA-1366) Remove need for an EMF from
OpenJPAPersistenceUtil and TraversableResolverImpl
[ https://issues.apache.org/jira/browse/OPENJPA-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods resolved OPENJPA-1366.
-----------------------------------
Resolution: Fixed
committed to trunk as r831406
> Remove need for an EMF from OpenJPAPersistenceUtil and TraversableResolverImpl
> ------------------------------------------------------------------------------
>
> Key: OPENJPA-1366
> URL: https://issues.apache.org/jira/browse/OPENJPA-1366
> Project: OpenJPA
> Issue Type: Improvement
> Components: validation
> Affects Versions: 2.0.0-M3
> Reporter: Donald Woods
> Assignee: Donald Woods
> Priority: Minor
> Fix For: 2.0.0-M4
>
>
> As pointed out by Pinaki and confirmed by Jeremy, we don't need an EMF for the isLoaded() call.
> From Pinaki - We can answer isLoaded() without really asking every broker to llok up in its cache or something. If the given instance pc is PersitenceCapable and has a non-null StateManager -- it is managed by us. If the question is: is pc managed by a specific EMF e, then also we can navigate from pc->sm->broker->brokerfactory->emf and compare by reference with e.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.