openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Woods (JIRA)" <j...@apache.org>
Subject [jira] Work started: (OPENJPA-1366) Remove need for an EMF from OpenJPAPersistenceUtil and TraversableResolverImpl
Date Fri, 30 Oct 2009 16:21:59 GMT

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

Work on OPENJPA-1366 started by Donald Woods.

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


Mime
View raw message