openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Vorburger (JIRA)" <j...@apache.org>
Subject [jira] Created: (OPENJPA-1416) FetchPlan doc should explicitly mention fetchPlan.removeFetchGroup(FetchGroup.NAME_DEFAULT);
Date Mon, 07 Dec 2009 21:40:18 GMT
FetchPlan doc should explicitly mention fetchPlan.removeFetchGroup(FetchGroup.NAME_DEFAULT);
--------------------------------------------------------------------------------------------

                 Key: OPENJPA-1416
                 URL: https://issues.apache.org/jira/browse/OPENJPA-1416
             Project: OpenJPA
          Issue Type: Bug
          Components: docs
    Affects Versions: 1.2.1
            Reporter: Michael Vorburger


As illustrated by the email exchange on http://openjpa.markmail.org/search/?q=#query:list%3Aorg.apache.openjpa.users+page:1+mid:vkmobafvjqojgtxg+state:results,
it does not seem to obvious (enough) for end-users that 

     fetchPlan.removeFetchGroup(FetchGroup.NAME_DEFAULT);

is required to configure FetchGroups "from scratch" (i.e. taking control of fetch groups completely,
e.g. in a framework built to exploit FetchGroups) in order to "override" any FetchType.EAGER
/ FetchType.LAZY annotation on the respective @Entity.

It would be nice if the OpenJPA doc, e.g. in http://openjpa.apache.org/builds/latest/docs/manual/ref_guide_fetch.html,
would more explicitly explain this with a few lines of blub, and a simple example code snippet
(see e.g. email exchange). 

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