From jdo-dev-return-8568-apmail-db-jdo-dev-archive=www.apache.org@db.apache.org Fri Apr 30 07:42:46 2010 Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 11576 invoked from network); 30 Apr 2010 07:42:45 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 30 Apr 2010 07:42:45 -0000 Received: (qmail 20845 invoked by uid 500); 30 Apr 2010 05:56:04 -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 20825 invoked by uid 99); 30 Apr 2010 05:56:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Apr 2010 05:56:03 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of awaisbajwa@gmail.com designates 74.125.83.44 as permitted sender) Received: from [74.125.83.44] (HELO mail-gw0-f44.google.com) (74.125.83.44) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Apr 2010 05:55:57 +0000 Received: by gwaa12 with SMTP id a12so5074791gwa.31 for ; Thu, 29 Apr 2010 22:55:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=Go9lovaRMx2vxfj3h+yMDwmDANsrZ4LWYiwTz0IdUhM=; b=mVVbghLOzqGUskTwbts2AZE2jk/jbssxEIuwSuJCBEGaHER/WhTh5BIZYNaY4CbuMw QgOQNXHpu0SXUwwRneuz4RkpEljQf8SMrKnVisT1FvMrWJ7DcTFkHehh2/cDZe4LeHpu ODIhjzUnnIMpZz5g70jDvi5bkykhl7rtbQXJI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=XYm6C0rK8uCq+Q0K6/D9huKppWwtqyqhd2U5clhUecNqRzhi8Rsu7qy/S3VXz47Ri7 4KFsUSszOUprpKDWeaJPH2SVlQ1wsYwPgqn4h4tCaaUhbvXR0xuJT5EpRpHagTD7ePXT yxfTVNGUJRAv7VbgM6clxnAPwI3GWNjEUjKZI= MIME-Version: 1.0 Received: by 10.150.55.24 with SMTP id d24mr3353552yba.186.1272606935762; Thu, 29 Apr 2010 22:55:35 -0700 (PDT) Received: by 10.100.131.4 with HTTP; Thu, 29 Apr 2010 22:55:35 -0700 (PDT) In-Reply-To: <720BC31B-A90B-45CB-B9F1-DA324F6451DB@oracle.com> References: <763FDC84-F785-4CEB-A7D0-CE1CA14B6006@oracle.com> <720BC31B-A90B-45CB-B9F1-DA324F6451DB@oracle.com> Date: Fri, 30 Apr 2010 01:55:35 -0400 Message-ID: Subject: Re: [VOTE] Release JDO.next Specification (was Review copy of JDO 2.3 with change bars and assertions) From: Awais Bajwa To: Craig L Russell Cc: JDO Expert Group , Apache JDO project Content-Type: multipart/alternative; boundary=000e0cd721765847f004856de425 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd721765847f004856de425 Content-Type: text/plain; charset=ISO-8859-1 Well , as I have seen in the specs ...I would definitly like to have it called JDO 3.0 and to release it Release JDO.next specification (the vote on the release artifacts will follow shortly; there are still a small number of issues to resolve) +1 Rename JDO.next to JDO 3.0. +1 Awais Bajwa On Thu, Apr 29, 2010 at 9:38 PM, Craig L Russell wrote: > I've looked at the changes for JDO 2.3 and I agree with others that the > changes are pretty significant in terms of new capabilities for tools and > users. > > Added an Enhancer API to allow applications to dynamically enhance classes. > Added a Metadata API to allow applications to query and create metadata for > classes. > Modified the behavior of getObjectById to allow the application to specify > the exact class of an instance, thereby avoiding a database access to > instantiate a persistent instance with a specific identity. > Added a datastore timeout that will cancel datastore operations that exceed > a user-specified time limit. > Added a query cancel that allows applications to cancel currently-executing > queries. > > The Enhancer API enables tools to be developed that support plugins for > ant, Eclipse, Netbeans, and other Java IDEs and tools to allow users to > enhance their classes during build, packaging, or runtime, without use of > proprietary APIs. > > The Metadata API enables tools to be developed to dynamically create Java > classes that map to existing SQL and NoSQL datastores and dynamically > specify the metadata for the mapping, without use of proprietary APIs. > > To me, this justifies renaming the release from JDO 2.3 to JDO 3.0. > > I'd like to run two votes simultaneously: > > Release JDO.next specification (the vote on the release artifacts will > follow shortly; there are still a small number of issues to resolve) > > Rename JDO.next to JDO 3.0. > > Please vote early and often. The last vote recorded for any person will > determine that person's vote. Polls are open now and will close no earlier > than May 6. > > Thanks, > > Craig > > On Apr 8, 2010, at 7:47 PM, Craig L Russell wrote: > > Hi, >> >> We're almost done with 2.3. Please take a look and see if there are any >> changes needed before we vote. >> >> Thanks, >> >> Craig >> >> For those only on the apache alias, please find the specification at: >> > > http://people.apache.org/~clr/jdo-2010-04-09.pdf >> > > Craig > >> >> Craig L Russell >> Architect, Oracle >> http://db.apache.org/jdo >> 408 276-5638 mailto:Craig.Russell@oracle.com >> P.S. A good JDO? O, Gasp! >> >> > Craig L Russell > Architect, Oracle > http://db.apache.org/jdo > 408 276-5638 mailto:Craig.Russell@oracle.com > P.S. A good JDO? O, Gasp! > > -- Awais Bajwa +1-862-222-6680 http://www.linkedin.com/pub/awais-bajwa/4/82a/2b9 --000e0cd721765847f004856de425--