Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 44779 invoked from network); 9 Mar 2006 01:04:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 9 Mar 2006 01:04:01 -0000 Received: (qmail 12093 invoked by uid 500); 9 Mar 2006 01:04:01 -0000 Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jdo-dev@db.apache.org Delivered-To: mailing list jdo-dev@db.apache.org Received: (qmail 12082 invoked by uid 99); 9 Mar 2006 01:04:01 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Mar 2006 17:04:01 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Mar 2006 17:04:00 -0800 Received: from ajax (localhost.localdomain [127.0.0.1]) by ajax (Postfix) with ESMTP id 83846D49FA for ; Thu, 9 Mar 2006 01:03:39 +0000 (GMT) Message-ID: <605805915.1141866219536.JavaMail.jira@ajax> Date: Thu, 9 Mar 2006 01:03:39 +0000 (GMT) From: "Craig Russell (JIRA)" To: jdo-dev@db.apache.org Subject: [jira] Resolved: (JDO-330) JPOX fails to populate fields in fetch plan during detachCopy In-Reply-To: <1073341880.1141694369996.JavaMail.jira@ajax> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/JDO-330?page=all ] Craig Russell resolved JDO-330: ------------------------------- Resolution: Invalid Assign To: Craig Russell This was a user error. The FetchPlan used the default MaxFetchDepth which is 1. None of the related instances' fields were set by the detach because of this error. This highlights an interesting usability issue with FetchPlan. The default FetchPlan MaxFetchDepth is designed to avoid accidentally retrieving the entire database into memory, but it needs to be carefully thought about. > JPOX fails to populate fields in fetch plan during detachCopy > ------------------------------------------------------------- > > Key: JDO-330 > URL: http://issues.apache.org/jira/browse/JDO-330 > Project: JDO > Type: Bug > Components: tck20 > Versions: JDO 2 rc1 > Environment: JPOX > Reporter: Craig Russell > Assignee: Craig Russell > Fix For: JDO 2 final > > After applying the patch in JDO-272, JPOX fails: > [java] 1) testDetachCopy(org.apache.jdo.tck.api.persistencemanager.detach.DetachCopy)javax.jdo.JDODetachedFieldAccessException: You have just attempted to access field "cart" yet this field was not detached when you detached the object. Either dont access this field, or detach the field when detaching the object. > [java] at org.apache.jdo.tck.pc.shoppingcart.CartEntry.jdoGetcart(CartEntry.java) > [java] at org.apache.jdo.tck.pc.shoppingcart.CartEntry.getCart(CartEntry.java:62) > [java] at org.apache.jdo.tck.api.persistencemanager.detach.DetachTest.checkCartValues(DetachTest.java:140) > [java] at org.apache.jdo.tck.api.persistencemanager.detach.DetachTest.checkCartValues(DetachTest.java:122) > [java] at org.apache.jdo.tck.api.persistencemanager.detach.DetachCopy.testDetachCopy(DetachCopy.java:68) > [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > [java] at org.apache.jdo.tck.JDO_Test.runBare(JDO_Test.java:206) > [java] at org.apache.jdo.tck.util.BatchTestRunner.start(BatchTestRunner.java:120) > [java] at org.apache.jdo.tck.util.BatchTestRunner.main(BatchTestRunner.java:95) > The field is part of the fetch plan in effect when the instances are detached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira