From dev-return-19598-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Thu Oct 13 13:51:04 2011 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 53D9196A9 for ; Thu, 13 Oct 2011 13:51:04 +0000 (UTC) Received: (qmail 16711 invoked by uid 500); 13 Oct 2011 13:51:04 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 16681 invoked by uid 500); 13 Oct 2011 13:51:04 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 16673 invoked by uid 99); 13 Oct 2011 13:51:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Oct 2011 13:51:04 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kwsutter@gmail.com designates 209.85.215.174 as permitted sender) Received: from [209.85.215.174] (HELO mail-ey0-f174.google.com) (209.85.215.174) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Oct 2011 13:50:57 +0000 Received: by eye27 with SMTP id 27so21606eye.33 for ; Thu, 13 Oct 2011 06:50:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=+LiA4Ol674gIw4MHWJRNKdq/XQINEuPpn2nN3dDB2KM=; b=iLLAn9mllMrT7CN41MeRe7V1JD4hGftRP5MyYytoleHEnDc3TxakCMgc5K5WsjeKD4 7O4C10/Q9B8D16Fade8VYZB92w6ZvLIomUAaEoL3pSbZzfKb75pJujSO2P7FqggvWNgg Yitlr6IRjiux3XzGv0JFqIF9mPgsqfibbkWnM= Received: by 10.14.16.219 with SMTP id h67mr373922eeh.148.1318513836096; Thu, 13 Oct 2011 06:50:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.14.186.1 with HTTP; Thu, 13 Oct 2011 06:50:16 -0700 (PDT) In-Reply-To: <1318512038501-6888872.post@n2.nabble.com> References: <1318436080290-6885650.post@n2.nabble.com> <1318512038501-6888872.post@n2.nabble.com> From: Kevin Sutter Date: Thu, 13 Oct 2011 08:50:16 -0500 Message-ID: Subject: Re: [DISCUSS] JDO usage end-of-life? To: dev@openjpa.apache.org Content-Type: multipart/alternative; boundary=0016e65a0e4cd4fbd904af2e6c33 X-Virus-Checked: Checked by ClamAV on apache.org --0016e65a0e4cd4fbd904af2e6c33 Content-Type: text/plain; charset=ISO-8859-1 Hi Pinaki, I haven't spent a great deal of time looking into this. But, you are probably right -- the JDO footprint is probably very small. I was just fishing to see how much interest there was in JDO -- just in case we would find some area of the code that is JDO-centric and it's either confusing, incorrect, or affecting performance. Thanks, Kevin On Thu, Oct 13, 2011 at 8:20 AM, Pinaki Poddar wrote: > Hi Kevin, > > OpenJPA project is for providing a JPA implementation, not a JDO > implementation. > OpenJPA is a misnomer :) > > Seriously speaking, what exactly do you suggest to remove to eol/get rid > of JDO? My read is that JDO-awareness has a very small footprint in terms > of > codelines. > > ----- > Pinaki Poddar > Chair, Apache OpenJPA Project > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/DISCUSS-JDO-usage-end-of-life-tp6876837p6888872.html > Sent from the OpenJPA Developers mailing list archive at Nabble.com. > --0016e65a0e4cd4fbd904af2e6c33--