Return-Path: 
 <users-return-9620-apmail-openjpa-users-archive=openjpa.apache.org@openjpa.apache.org>
X-Original-To: apmail-openjpa-users-archive@minotaur.apache.org
Delivered-To: apmail-openjpa-users-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id B1695902E
	for <apmail-openjpa-users-archive@minotaur.apache.org>;
 Tue, 11 Oct 2011 02:22:09 +0000 (UTC)
Received: (qmail 87598 invoked by uid 500); 11 Oct 2011 02:22:09 -0000
Delivered-To: apmail-openjpa-users-archive@openjpa.apache.org
Received: (qmail 87444 invoked by uid 500); 11 Oct 2011 02:22:09 -0000
Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@openjpa.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@openjpa.apache.org>
List-Post: <mailto:users@openjpa.apache.org>
List-Id: <users.openjpa.apache.org>
Reply-To: users@openjpa.apache.org
Delivered-To: mailing list users@openjpa.apache.org
Received: (qmail 87347 invoked by uid 99); 11 Oct 2011 02:22:09 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Oct 2011 02:22:08 +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 michael.d.dick@gmail.com
 designates 209.85.161.174 as permitted sender)
Received: from [209.85.161.174] (HELO mail-gx0-f174.google.com)
 (209.85.161.174)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Oct 2011 02:22:02 +0000
Received: by ggnv2 with SMTP id v2so6756383ggn.33
        for <multiple recipients>; Mon, 10 Oct 2011 19:21:41 -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=ph74M+OPJNgJByEC9htLEa1QUIl+Be9FW0s4JNQQtb8=;
        b=Cwkb0tJqoJ+kCcJn3ipkiuuVSjECaQl1Yj4a8weHuMu4uZmpk/D4PGjjjW9SXZyCIa
         ZSXD50mTe3Nj+g6mYA5TXCzOYKpPks2wNwsIM8vilRqcwqhEsqGlmSubBqCklDqnp23t
         vGpYws6GLFxQxjB7xfL8QvOce93ficBsq7EtA=
Received: by 10.101.131.23 with SMTP id i23mr4146801ann.17.1318299701140; Mon,
 10 Oct 2011 19:21:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.210.17 with HTTP; Mon, 10 Oct 2011 19:21:20 -0700 (PDT)
In-Reply-To: 
 <CABH8ermshdOzoXCJKuS8tv6aZ9y4nCD+m6ZR_zMh_bsHZ6LSUg@mail.gmail.com>
References: 
 <CABH8ermshdOzoXCJKuS8tv6aZ9y4nCD+m6ZR_zMh_bsHZ6LSUg@mail.gmail.com>
From: Michael Dick <michael.d.dick@gmail.com>
Date: Mon, 10 Oct 2011 21:21:20 -0500
Message-ID: 
 <CAGNTB4S=R-dC77hn2=9sRGV9ji2wbbtnVHo8PdhXNo0vzcrKfA@mail.gmail.com>
Subject: Re: [DISCUSS] JDO usage end-of-life?
To: users@openjpa.apache.org, dev@openjpa.apache.org
Content-Type: multipart/alternative; boundary=001636c5c10b64dde204aefc91d8
X-Virus-Checked: Checked by ClamAV on apache.org

--001636c5c10b64dde204aefc91d8
Content-Type: text/plain; charset=ISO-8859-1

There is at least some interest from a subset of our users. Matthew Adams
and issue: OPENJPA-1744
<https://issues.apache.org/jira/browse/OPENJPA-1744>to add support for
JDO last July. I closed the issue, but Matthew responded
and the issue was reopened.

There hasn't been a lot of activity on the JIRA since then. There are some
users watching it, but no one has voted for it. If there's an outpouring of
support from the users list, and a committer (or aspiriing committer) is
interested in championing the effort, I'd be all for adding a JDO persona.
Absent a champion who is ready to dive into the code, I think that we should
clean up the references to jdo.

Even if OpenJPA removes the references to JDO, I'm sure a separate module
could be written that sits on top of our binaries. I suspect that's what BEA
/ Oracle did.

-mike



On Mon, Oct 10, 2011 at 8:18 AM, Kevin Sutter <kwsutter@gmail.com> wrote:

> Hi,
> Sorry to cross post to both forums, but I wanted to ensure that I hit
> everybody that might have an opinion on this JDO topic...
>
> Is the JDO personality of OpenJPA still being utilized?  Marc's recent post
> about possibly pulling in javax.jdo.* packages during the enhancement
> processing [1] reminded me that we still have old remnants of JDO (and
> Kodo)
> in the OpenJPA code base.  OpenJPA has never claimed support for JDO (nor
> Kodo).  Way back when, BEA provided a JDO implementation as part of their
> offering that sat on top of OpenJPA.  As far as I know, BEA (and Oracle)
> only support the 1.1.x service stream of OpenJPA.  So, if we did this in
> the
> 2.x stream, there should be no effects to that set of users.
>
> Would there be a concern with the current users of OpenJPA to clean up the
> code base and remove these JDO/Kodo references?  From a JPA/OpenJPA
> perspective, you should see no differences in functionality.
>
> Like I said, Marc's posting prompted me to revisit this topic.  I'm just
> exploring the option with no immediate plans of actually doing the work...
>
> Thanks,
> Kevin
>
> [1]
>
> http://openjpa.208410.n2.nabble.com/weird-JDO-Exception-when-using-OpenJPA-2-Enhancer-tc6870122.html
>

--001636c5c10b64dde204aefc91d8--