openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pinaki Poddar" <ppod...@bea.com>
Subject RE: [jira] Created: (OPENJPA-438) The manual refers to FetchPlan (a JDO interface) while the OpenJPA interface is FetchConfiguration
Date Fri, 09 Nov 2007 04:13:41 GMT
The user/application level interface is
org.apache.openjpa.persistence.FetchPlan.
It is obtainable from OpenJPAEntityManager.getFetchPlan()

org.apache.openjpa.kernel.FetchConfiguration is the internal
(cannonical, spec-independent) interface that the broker understands.

FetchPlan implementations are thin delegate-style wrappers to
FetchConfiguration implementation.

FetchConfiguration should not be visible to the user. Is it exposed
somehow/somewhere to the user code?

 

-----Original Message-----
From: Craig Russell (JIRA) [mailto:jira@apache.org] 
Sent: Thursday, November 08, 2007 7:15 PM
To: dev@openjpa.apache.org
Subject: [jira] Created: (OPENJPA-438) The manual refers to FetchPlan (a
JDO interface) while the OpenJPA interface is FetchConfiguration

The manual refers to FetchPlan (a JDO interface) while the OpenJPA
interface is FetchConfiguration
------------------------------------------------------------------------
--------------------------

                 Key: OPENJPA-438
                 URL: https://issues.apache.org/jira/browse/OPENJPA-438
             Project: OpenJPA
          Issue Type: Bug
          Components: docs
    Affects Versions: 1.0.0
            Reporter: Craig Russell


We need to change the manual to refer to FetchConfiguration and remove
references to FetchPlan if it is not implemented.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Notice:  This email message, together with any attachments, may contain information  of  BEA
Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,
 copyrighted  and/or legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient, and have received
this message in error, please immediately return this by email and then delete it.

Mime
View raw message