Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Received-SPF: pass (athena.apache.org: domain of kwsutter@gmail.com designates
 209.85.215.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1318436080290-6885650.post@n2.nabble.com>
References: 
 <CABH8ermshdOzoXCJKuS8tv6aZ9y4nCD+m6ZR_zMh_bsHZ6LSUg@mail.gmail.com>
 <1318436080290-6885650.post@n2.nabble.com>
From: Kevin Sutter <kwsutter@gmail.com>
Date: Wed, 12 Oct 2011 13:55:09 -0500
Message-ID: 
 <CABH8ernzqLcaUPY4vQoR5ORuwZscY43cSnNgPxpqXUHZtzgB=Q@mail.gmail.com>
Subject: Re: [DISCUSS] JDO usage end-of-life?
To: dev@openjpa.apache.org
Content-Type: multipart/alternative; boundary=0016e65a0e4c58c87c04af1e91c4

--0016e65a0e4c58c87c04af1e91c4
Content-Type: text/plain; charset=ISO-8859-1

Hi Pinaki,
I can see validity in all of your stated reasons.  But, the OpenJPA project
is for providing a JPA implementation, not a JDO implementation.  If
somebody wants to spin off and support their own "OpenJDO" implementation
that is based on OpenJPA or its kernel, then all the more power to them.  I
am just questioning why we should continue to work around or with JDO
idiosyncrasies with our JPA implementation.

Thanks,
Kevin

On Wed, Oct 12, 2011 at 11:14 AM, Pinaki Poddar <ppoddar@apache.org> wrote:

> I do not see need to remove JDO support from OpenJPA for following reasons
>
> a) there are current JDO usage/users -- may not be as predominant as JPA
> community, but they are there.
> Google AppEngine environment, for example, supports JDO for persistent
> services. I have also seen active JDO users in this forum.
>
> b) OpenJPA architecture had always maintained the goal of being
> facade-agnostic (i.e. JPA, JDO or something else) and datastore-agnostic
> (i.e. whether JDBC or NoSQL or OODB). That goal was not easy to achieve but
> had been executed with a degree of discipline that, imo, is one of its
> unique and key strength. Letting go that primary strength would not be a
> positive step.
>
> c) I have come across migration scenarios where an existing JDO schema is
> being ported to JPA schema. Those use cases may be even more frequent as
> JPA
> gains more traction. Such migration scenario are supported in current
> model.
>
> d) The reported error that prompted this discussion is not a critical
> failure. Possibly could be fixed with moderate effort. It does not seem to
> indicate that we should throw JDO under the bus.
>
>
> -----
> Pinaki Poddar
> Chair, Apache OpenJPA Project
> --
> View this message in context:
> http://openjpa.208410.n2.nabble.com/DISCUSS-JDO-usage-end-of-life-tp6876837p6885650.html
> Sent from the OpenJPA Developers mailing list archive at Nabble.com.
>

--0016e65a0e4c58c87c04af1e91c4--