Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 42865 invoked from network); 10 Sep 2006 18:21:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 Sep 2006 18:21:01 -0000 Received: (qmail 40148 invoked by uid 500); 10 Sep 2006 18:21: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 40137 invoked by uid 99); 10 Sep 2006 18:21:01 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Sep 2006 11:21:01 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Sep 2006 11:21:00 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id BC45C7142C7 for ; Sun, 10 Sep 2006 18:17:22 +0000 (GMT) Message-ID: <20465486.1157912242752.JavaMail.jira@brutus> Date: Sun, 10 Sep 2006 11:17:22 -0700 (PDT) From: "Michael Bouschen (JIRA)" To: jdo-dev@db.apache.org Subject: [jira] Commented: (JDO-423) Missing addTearDownClass in org.apache.jdo.tck.query.jdoql.variables.VariablesWithoutExtent In-Reply-To: <14563396.1157851342270.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 X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/JDO-423?page=comments#action_12433718 ] Michael Bouschen commented on JDO-423: -------------------------------------- Hi Ilan, you input is highly appreciated. What kind of issue are you running into with cleaning up the NoExtent instances? I'm not sure whether moving addTearDownInstance to the beginning of the method would make any difference. Method addTearDownInstance retrieves the oid of the parameter instance and stores it in a local set. At cleanup time method tearDown iterates the list of registered oids, retrieves the pc instances using getObjectById and calls pm.deletePersistent to remove the instance. But if the pm.deletePersistent fails, the TCK is in trouble, because it cannot cleanup the database to prepare the next run. Do you have an idea what to do? Regards Michael > Missing addTearDownClass in org.apache.jdo.tck.query.jdoql.variables.VariablesWithoutExtent > ------------------------------------------------------------------------------------------- > > Key: JDO-423 > URL: http://issues.apache.org/jira/browse/JDO-423 > Project: JDO > Issue Type: Bug > Components: tck20 > Affects Versions: JDO 2 final > Reporter: Ilan Kirsh > Priority: Minor > > Lines 101- 108, instead of: > protected void localSetUp() { > addTearDownClass(CompanyModelReader.getTearDownClasses()); > loadAndPersistCompanyModel(getPM()); > NoExtent noExtent = new NoExtent(1); > makePersistent(noExtent); > addTearDownInstance(noExtent); > } > should be: > protected void localSetUp() { > addTearDownClass(CompanyModelReader.getTearDownClasses()); > addTearDownClass(NoExtent.class); // Added missing addTearDownClass > loadAndPersistCompanyModel(getPM()); > NoExtent noExtent = new NoExtent(1); > makePersistent(noExtent); > addTearDownInstance(noExtent); > } -- 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