Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: open-jpa-dev@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: domain of plinskey@bea.com designates
 63.96.176.25 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: State of OpenJPA code drop
Date: Fri, 28 Jul 2006 13:14:13 -0700
Message-ID: <7D856CDFE035FF45A0420ACBD71BDD63019CBF32@repbex02.amer.bea.com>
In-Reply-To: <89c0c52c0607270730tc98be42n23259f17f5f4f8e1@mail.gmail.com>
Thread-Topic: State of OpenJPA code drop
Thread-Index: AcaxiUdxoTqL1ZZuSLi8rBhARVQW2QA+DVXQ
From: "Patrick Linskey" <plinskey@bea.com>
To: <open-jpa-dev@incubator.apache.org>

Things should be at a steady state. We've got oodles of tests that we'll
want to get out into Apache at some point. But the team at BEA is
currently focused more on making our tests pass again and finishing
reassembling Kodo on top of OpenJPA than on pulling out test
infrastructure.

Feature-wise, I'm sure we'll see some more code come out with
interesting features, but what you see now is substantially all of
what's currently in plan.

Regarding CTS: we haven't yet set up anything that tests just OpenJPA
against the JPA TCK. Also, I'm really not sure how much I'm allowed to
say about TCK status based on runs using BEA's tests. I do think that I
can say this: the BEA Kodo automated testing system includes the JPA
TCK, Kodo 4.0 passed the JPA TCK, and we're working as we speak on
getting Kodo 4.1 (based on OpenJPA) to get to the same success level in
the Kodo automated testing system as Kodo 4.0 was at.

-Patrick

--=20
Patrick Linskey
BEA Systems, Inc.=20=20

> -----Original Message-----
> From: Kevin Sutter [mailto:kwsutter@gmail.com]=20
> Sent: Thursday, July 27, 2006 7:30 AM
> To: open-jpa-dev@incubator.apache.org
> Subject: State of OpenJPA code drop
>=20
> Hi Patrick,
> Now that the code drops seem to be slowing down a bit, I'm=20
> wondering whether you can give me an update on the=20
> "completeness" of the OpenJPA code repository.  I'm=20
> attempting to verify some of the expected functionality and=20
> I'm failing a few test scenarios.  I'm just wondering whether=20
> the majority of the code has now been dropped, and whether we=20
> can start to post questions and/or bug reports.  But, if=20
> there's more to come, then I'd like to understand the state=20
> of the repository.
>=20
> For example, is the OpenJPA JPQL query engine complete?  I'm=20
> hitting some failures with query statement parsing, type=20
> conversions, database pushdowns, etc.  Before posting more=20
> detailed information about these failures, I'm wondering=20
> whether it's complete yet or not.
>=20
> Related to this is the execution of the CTS OpenJPA TCK.  It=20
> looks like some basic problems with getting the dynamic=20
> runtime class enhancer to work properly.  Here again, not=20
> sure if this is a configuration problem, or insufficient code=20
> drop, or real problems.  Do you have any personal experience=20
> with executing the TCK that you could share?
>=20
> Thanks for your help!
>=20
> Kevin
>=20
_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.