Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 88511 invoked from network); 20 Oct 2005 10:02:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 20 Oct 2005 10:02:57 -0000 Received: (qmail 53537 invoked by uid 500); 20 Oct 2005 10:02:57 -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 53526 invoked by uid 99); 20 Oct 2005 10:02:56 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Oct 2005 03:02:56 -0700 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [216.148.213.132] (HELO smtp.mailix.net) (216.148.213.132) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Oct 2005 03:02:55 -0700 Received: from [192.168.8.8] (helo=localhost) by smtp.mailix.net with asmtp (Exim 4.24-CA) id 1ESXFm-0000ea-1W for jdo-dev@db.apache.org; Thu, 20 Oct 2005 03:02:30 -0700 Received: from uu194-7-80-34.unknown.be.uu.net (uu194-7-80-34.unknown.be.uu.net [194.7.80.34]) by webmail.jpox.org (IMP) with HTTP for ; Thu, 20 Oct 2005 03:02:29 -0700 Message-ID: <1129802549.43576b35f0bff@webmail.jpox.org> Date: Thu, 20 Oct 2005 03:02:29 -0700 From: erik@jpox.org To: jdo-dev@db.apache.org References: <4357670E.8080809@spree.de> In-Reply-To: <4357670E.8080809@spree.de> MIME-Version: 1.0 User-Agent: Internet Messaging Program (IMP) 3.2.3 X-Originating-IP: 194.7.80.34 X-SA-Exim-Mail-From: erik@jpox.org Subject: Re: Non-serializable object id classes Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on westvirginia.backend X-Spam-Level: *** X-SA-Exim-Version: 3.1 (built Thu Oct 23 13:26:47 PDT 2003) X-SA-Exim-Scanned: Yes X-uvscan-result: clean (1ESXFm-0000ea-1W) X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Status: No, score=3.5 required=10.0 tests=HELO_DYNAMIC_IPADDR, J_CHICKENPOX_31,NO_REAL_NAME autolearn=no version=3.0.2 X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Michael, JPOX raises InvalidPrimaryKeyException if the id class is not Serializable. Your class should not get enhanced and the cause is logged (log4j). If you want, enable log4j to write to the console. Quoting Michael Watzek : > Craig, > > I am unsure about chapter "5.4.1 Application (primary key) identity" in > the spec (version 9/9/2005). That chapter requires "... JDO object id > has all of the characteristics of an RMI remote object, ...". One > sentence further the spec specifies: > > "A5.4.1-3 REMOVE THIS ASSERTION [...]" > > Part of that assertion is the requirement on object id classes to be > serializable. > > The TCK does not implement this assertion. Does this mean, that it is > valid to specify non-serializable object id classes? > > Andy, Erik, > > if I call the JPOX enhancer for a class (among others) having > application identity and the object identity class is not serializable, > then the enhancement process silently exits without any (error) > messages. Also, there is no exit code indicating an error. As a > consequence, no classes are enhanced. Would it make sense to write a > warning (or error) message to the console indicating the problem? > > Regards, > Michael > -- > ------------------------------------------------------------------- > Michael Watzek Tech@Spree Engineering GmbH > mailto:mwa.tech@spree.de Buelowstr. 66 > Tel.: ++49/30/235 520 36 10783 Berlin - Germany > Fax.: ++49/30/217 520 12 http://www.spree.de/ > ------------------------------------------------------------------- >