You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Craig Russell (JIRA)" <ji...@apache.org> on 2007/11/09 04:14:50 UTC
[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.
RE: [jira] Created: (OPENJPA-438) The manual refers to FetchPlan (a JDO interface) while the OpenJPA interface is FetchConfiguration
Posted by Pinaki Poddar <pp...@bea.com>.
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.
[jira] Resolved: (OPENJPA-438) The manual refers to FetchPlan (a
JDO interface) while the OpenJPA interface is FetchConfiguration
Posted by "Pinaki Poddar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pinaki Poddar resolved OPENJPA-438.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.3.0
org.apache.openjpa.persistence.FetchPlan is the the JPA facade level, user visible interface.
org.apache.openjpa.kernel.FetchConfiguration is the kernel level interface.
I think the doc is OK -- hence resolving it.
Please reopen if something is amiss.
> 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
> Fix For: 1.3.0
>
>
> 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.