Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 28858 invoked from network); 23 Oct 2007 14:44:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Oct 2007 14:44:45 -0000 Received: (qmail 11714 invoked by uid 500); 23 Oct 2007 14:44:30 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 11673 invoked by uid 500); 23 Oct 2007 14:44:30 -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 11599 invoked by uid 99); 23 Oct 2007 14:44:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Oct 2007 07:44:30 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Oct 2007 14:44:41 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 42903714241 for ; Tue, 23 Oct 2007 07:43:51 -0700 (PDT) Message-ID: <1078995.1193150631270.JavaMail.jira@brutus> Date: Tue, 23 Oct 2007 07:43:51 -0700 (PDT) From: "Patrick Linskey (JIRA)" To: dev@openjpa.apache.org Subject: [jira] Reopened: (OPENJPA-370) LoadFetchGroup annotation was not recognized during the fetch1 In-Reply-To: <24890419.1189786052046.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/OPENJPA-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey reopened OPENJPA-370: ------------------------------------- It looks like this patch might have a performance impact due to the additional time required to compute field inclusion. We should consider other implementation routes or potentially rolling this back on the 1.0.x branch prior to 1.0.1, depending on what we decide our release criteria should be. > LoadFetchGroup annotation was not recognized during the fetch1 > -------------------------------------------------------------- > > Key: OPENJPA-370 > URL: https://issues.apache.org/jira/browse/OPENJPA-370 > Project: OpenJPA > Issue Type: Bug > Components: kernel > Affects Versions: 1.0.1, 1.1.0 > Reporter: Teresa Kan > Assignee: Teresa Kan > Fix For: 1.0.1, 1.1.0 > > Attachments: OPENJPA_370_2.patch, TestFetchGroup.zip > > > Employee class has a LoadFetchGroup annotation defined on the Rating field, when getRating was called, the address should be returned also. However, openjpa did not handle the LoadFetchGroup correctly, therefore, address was not eargly fetched. > public class FGEmployee{ > @Id > private int id; > > @OneToOne(fetch=FetchType.LAZY) > private FGAddress address; > > @Basic(fetch=FetchType.LAZY) > @LoadFetchGroup("AddressFetchGroup") > private String rating; > > @ManyToOne(fetch=FetchType.LAZY) > private FGManager manager; > .. > } -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.