Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 92951 invoked from network); 26 Jul 2007 19:33:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Jul 2007 19:33:12 -0000 Received: (qmail 23833 invoked by uid 500); 26 Jul 2007 19:33:11 -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 23787 invoked by uid 99); 26 Jul 2007 19:33:11 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jul 2007 12:33:11 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [212.159.14.132] (HELO pih-relay05.plus.net) (212.159.14.132) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jul 2007 12:33:08 -0700 Received: from [87.113.81.79] (helo=[192.168.0.22]) by pih-relay05.plus.net with esmtp (Exim) id 1IE94l-0003sC-5u; Thu, 26 Jul 2007 20:32:43 +0100 From: Andy Jefferson To: jdo-dev@db.apache.org Subject: Re: [jira] Commented: (JDO-510) Remove @Field and @Property and replace them with @Persistent Date: Thu, 26 Jul 2007 20:32:41 +0100 User-Agent: KMail/1.9.6 Cc: JDO Expert Group References: <30106273.1185406471287.JavaMail.jira@brutus> <200707260932.23826.andy@jpox.org> <2A196681-F8FC-4BD1-87FD-307908964D71@SUN.com> In-Reply-To: <2A196681-F8FC-4BD1-87FD-307908964D71@SUN.com> Organization: JPOX MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200707262032.42135.andy@jpox.org> X-Virus-Checked: Checked by ClamAV on apache.org Hi Craig, > The issue here is if both type and types are specified, which one > wins? Since types can be both single or multiple types, I think > there's less opportunity for error if there is only one element, and > types does it. And it is evocative of the notion that even though you > specified a type on your field/property (or not, for unadorned > collection/map types), there are more constraints on the actual types > that you can put into it. No problem with just having the "types" element for me ... that's what I ha= d=20 originally :-). What the user types @Element(types=3DMyElement.class) compared to the single form @Element(type=3DMyElement.class) is so similar I didn't see the point of the single form variant and, of=20 course, it also allows multiple values for implementations that support it.= =20 Just want to avoid that option being included and then removed, and then ba= ck=20 in again. > Meantime, I'll check in the change from boundTypes to types to keep thing= s=20 > moving.=20 Thx.=20 JPOX CVS now builds with latest Apache JDO jdo2-api.jar=20 (@Persistent,@Element,@Key,@Value "boundTypes" -> "types", and also=20 @Element,@Key,@Value "embedded" change). I've started the "nightly" build=20 running so there are jars if anyone wants to run with it. =2D-=20 Andy =A0(Java Persistent Objects - http://www.jpox.org)