From dev-return-6768-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Fri Nov 09 04:14:16 2007 Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 49162 invoked from network); 9 Nov 2007 04:14:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Nov 2007 04:14:16 -0000 Received: (qmail 90359 invoked by uid 500); 9 Nov 2007 04:14:04 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 90329 invoked by uid 500); 9 Nov 2007 04:14:04 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 90320 invoked by uid 99); 9 Nov 2007 04:14:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Nov 2007 20:14:04 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ppoddar@bea.com designates 66.248.192.39 as permitted sender) Received: from [66.248.192.39] (HELO repmmg02.bea.com) (66.248.192.39) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Nov 2007 04:14:07 +0000 Received: from repmmr02.bea.com (repmmr02.bea.com [10.160.30.72]) by repmmg02.bea.com (Switch-3.3.0/Switch-3.2.7) with ESMTP id lA94DjwF018348 for ; Thu, 8 Nov 2007 20:13:45 -0800 Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by repmmr02.bea.com (Switch-3.3.0/Switch-3.2.7) with ESMTP id lA94DhUU022467 for ; Thu, 8 Nov 2007 20:13:43 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: RE: [jira] Created: (OPENJPA-438) The manual refers to FetchPlan (a JDO interface) while the OpenJPA interface is FetchConfiguration Date: Thu, 8 Nov 2007 20:13:41 -0800 Message-ID: <3992B07C0590B548BB294D31768A1DA29BC5C7@repbex01.amer.bea.com> In-Reply-To: <29060672.1194578090891.JavaMail.jira@brutus> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [jira] Created: (OPENJPA-438) The manual refers to FetchPlan (a JDO interface) while the OpenJPA interface is FetchConfiguration Thread-Index: AcgifsPkCWTfuMOzQxqpSvPeD0gKnQAB7RaQ References: <29060672.1194578090891.JavaMail.jira@brutus> From: "Pinaki Poddar" To: x-BEA-PMX-Instructions: AV x-BEA-MM: Internal-To-External X-Virus-Checked: Checked by ClamAV on apache.org 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.