Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 20038 invoked from network); 5 Aug 2005 18:23:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 5 Aug 2005 18:23:21 -0000 Received: (qmail 32857 invoked by uid 500); 5 Aug 2005 18:23:21 -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 32844 invoked by uid 99); 5 Aug 2005 18:23:20 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Aug 2005 11:23:20 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [81.174.133.99] (HELO roobarb.ajsoft.net) (81.174.133.99) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Aug 2005 11:23:11 -0700 Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by roobarb.ajsoft.net (Postfix) with ESMTP id B347511125 for ; Fri, 5 Aug 2005 19:23:13 +0100 (BST) From: Andy Jefferson To: jdo-dev@db.apache.org Subject: Re: Minutes: JDO TCK Conference Call Friday, Aug 5, 9 am PST Date: Fri, 5 Aug 2005 19:23:12 +0100 User-Agent: KMail/1.7.2 References: <42DFF7BB.4070407@sun.com> <200508051851.56730.andy@jpox.org> In-Reply-To: Organization: JPOX MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508051923.12929.andy@jpox.org> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N > I assume that this is the cause of the JDO-107 error: > JDODataStoreException: Cannot set Long parameter: value = null > > Since you don't support serializing the object, you're trying to > write the key to the column. Hi Craig, Yep. Fuller error messages so people can identify the column causing the problem will be in next nightly build. -- Andy