Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 97781 invoked from network); 30 Nov 2005 05:02:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 30 Nov 2005 05:02:10 -0000 Received: (qmail 47764 invoked by uid 500); 30 Nov 2005 05:02:09 -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 Delivered-To: moderator for jdo-dev@db.apache.org Received: (qmail 97654 invoked by uid 99); 29 Nov 2005 06:33:04 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) From: Andy Jefferson To: Tony Lai Subject: Re: Questions on detach/attach and setDetachAllOnCommit Date: Tue, 29 Nov 2005 07:32:37 +0100 User-Agent: KMail/1.7.2 Cc: Craig L Russell , Apache JDO project , JDO Expert Group References: <001d01c5f42b$4bc7bf00$8902a8c0@P7I1H5> <001e01c5f4ac$b5533a90$8902a8c0@P7I1H5> In-Reply-To: <001e01c5f4ac$b5533a90$8902a8c0@P7I1H5> Organization: JPOX MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511290732.37663.andy@jpox.org> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi Tony, > I only define the fetch-group "group1" because the fetch-depth defined in > the class field does not work, and JPOX developers (Andy in this case) is > not clear what the expectation is since it is not defined in the spec. Can > you add a little clearification to the spec on this issue, please? I'm actually well aware of what has been discussed in the EG. I simply have no plans on implementing a new definition of a feature in JPOX until I have a spec in front of me that defines it. JPOX has implemented many things in the past that have featured in specs and then have changed. We have plenty of other things to work on to not be implementing changes that have no written definition yet. When Craig provides the next spec with the discussed definition of fetch-depth it will be implemented by us. -- Andy