From jdo-dev-return-6531-apmail-db-jdo-dev-archive=www.apache.org@db.apache.org Sat Sep 29 17:18:01 2007 Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 18470 invoked from network); 29 Sep 2007 17:18:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Sep 2007 17:18:00 -0000 Received: (qmail 77509 invoked by uid 500); 29 Sep 2007 17:17:50 -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 77498 invoked by uid 99); 29 Sep 2007 17:17:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 29 Sep 2007 10:17:50 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [212.150.49.172] (HELO mtaout2.barak.net.il) (212.150.49.172) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 29 Sep 2007 17:17:50 +0000 Received: from ILANC ([89.1.144.35]) by mtaout2.barak.net.il (Sun Java System Messaging Server 6.2-7.04 (built Aug 17 2006)) with ESMTPA id <0JP50014K3UUV1C0@mtaout2.barak.net.il> for jdo-dev@db.apache.org; Sat, 29 Sep 2007 19:13:43 +0200 (IST) Date: Sat, 29 Sep 2007 19:11:57 +0200 From: Ilan Kirsh Subject: Re: Minutes: JDO TCK Conference Call Friday, Sep 28 , 9 am PDT To: jdo-dev@db.apache.org Cc: jdo-experts-ext@Sun.COM Reply-to: Ilan Kirsh Message-id: <00d601c802bc$11e90450$0500000a@ILANC> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 X-Mailer: Microsoft Outlook Express 6.00.2900.3138 Content-type: text/plain; format=flowed; charset=windows-1255; reply-type=response Content-transfer-encoding: 7bit X-Priority: 3 X-MSMail-priority: Normal References: <4463CFBC.2050403@sun.com> <45A7119B.30601@sun.com> <45B01041.10106@sun.com> <45B95F3A.8090006@sun.com> <45CBC6A8.8030101@sun.com> <45D4E5E7.2050505@sun.com> <45DE3995.7070404@sun.com> <45E70D47.2040700@sun.com> <45F097C5.6020403@sun.com> <45F9D2EE.4070802@sun.com> <4603598C.8080205@sun.com> <460C4010.50209@sun.com> <46159A52.30506@sun.coom> <461EC15F.4070600@sun.ccom> <4627E706.6010105@sun.com> <463145A4.5080003@sun.com> <463A7B49.7000905@sun.com> <464CD0EB.5010101@sun.com> <46565157.4070804@sun.com> <465F4B00.9060906@sun.com> <4668D1DE.1080105@sun.com> <4671BA1B.7080600@sun.com> <467AFECA.6050104@sun.com> <468452A4.7080404@sun.com> <4696A846.1000707@sun.com> <469FFFEE.9030303@sun.com> <46AA0FE7.9060102@sun.com> <412A2419-D8FE-438F-A503-373D72DB3199@SUNN.com> <46C52BB6.5040305@sun.com> <46D76C3C.6020903@sun.com> <46E0C4C8.5050103@sun.com> <46E9CA09.1070408@sun.com> <46F33ED0.8050005@sun.com> <46FC1E63.2040605@sun.com> X-Virus-Checked: Checked by ClamAV on apache.org Hi Craig, > 2. Test challenges. Some challenges have been filed by Ilan. Most > have been fixed in 2.1 maintenance (trunk) and one of them is > unresolved but can be fixed in the challenge resolution branch 2.0.1 > interim to a final fix in 2.1 maintenance. > > Clarification: The 2.1 maintenance work is being done on the trunk. > We created a 2.0.1 branch that has no API changes from 2.0 but has > fixes for the tck where a specification clarification or API change > would be needed to pass the tck. A compliant JDO 2.0 implementation > should be able to pass the latest tck test in the 2.0.1 branch. I am not sure I understand this. Currently it is impossible for a compliant JDO implementation to pass the latest tck tests in the 2.0.1 branch. For instance, look at: http://issues.apache.org/jira/browse/JDO-529 As you explained very well in a comment to this issue on 16 Sep 2007, an implementation should return 4 result objects rather than 3. I suggest adding these 5 tests to the exclude list of branch 2.0.1. Otherwise, until the release of JDO 2.1 no implementation can be JDO compliance (unfortunately including the reference implementation), because you can only pass the tests by violating the specification. Regards, Ilan