From open-jpa-dev-return-267-apmail-incubator-open-jpa-dev-archive=incubator.apache.org@incubator.apache.org Tue Aug 08 21:52:18 2006 Return-Path: Delivered-To: apmail-incubator-open-jpa-dev-archive@locus.apache.org Received: (qmail 56487 invoked from network); 8 Aug 2006 21:52:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 8 Aug 2006 21:52:18 -0000 Received: (qmail 57273 invoked by uid 500); 8 Aug 2006 21:52:18 -0000 Delivered-To: apmail-incubator-open-jpa-dev-archive@incubator.apache.org Received: (qmail 57209 invoked by uid 500); 8 Aug 2006 21:52:17 -0000 Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: open-jpa-dev@incubator.apache.org Delivered-To: mailing list open-jpa-dev@incubator.apache.org Received: (qmail 57200 invoked by uid 99); 8 Aug 2006 21:52:17 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Aug 2006 14:52:17 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [66.116.97.229] (HELO mail.dudney.net) (66.116.97.229) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Aug 2006 14:52:17 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.dudney.net (Postfix) with ESMTP id 71AD62DF50C for ; Tue, 8 Aug 2006 15:51:54 -0600 (MDT) Received: from mail.dudney.net ([127.0.0.1]) by localhost (mini.dudney.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26004-01 for ; Tue, 8 Aug 2006 15:51:16 -0600 (MDT) Received: from [192.168.1.101] (c-24-9-189-43.hsd1.co.comcast.net [24.9.189.43]) by mail.dudney.net (Postfix) with ESMTP id D99742DF4EE for ; Tue, 8 Aug 2006 15:51:13 -0600 (MDT) Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: References: <7D856CDFE035FF45A0420ACBD71BDD63019CBF32@repbex02.amer.bea.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <21A0CFDB-2292-4841-8380-EE4D110D927D@apache.org> Content-Transfer-Encoding: 7bit From: Bill Dudney Subject: Re: State of OpenJPA code drop Date: Tue, 8 Aug 2006 15:51:13 -0600 To: open-jpa-dev@incubator.apache.org X-Mailer: Apple Mail (2.752.2) X-Virus-Scanned: by amavisd-new at dudney.net X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi All, On MyFaces (and I'm hoping here and @ cayenne) we set up a tck maling list to discuss the issues that the TCK points out. TTFN, -bd- On Aug 8, 2006, at 3:44 PM, Craig L Russell wrote: > Hi Patrick, > > On Jul 28, 2006, at 1:14 PM, Patrick Linskey wrote: >> >> 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. > > I'm sure you have some ideas for features that are not currently > part of the code drop that you think might be good candidates for > the community; e.g. someone had an idea to add the PU name to > logging messages. I'd like to suggest that for better transparency, > each of these things should be put into JIRA with some suggestion > what the implementation might look like and what kind of unit > testing might be done. Then, if someone wants to work on it, they > assign it to themselves in JIRA and if they need help, post on the > dev alias for support. >> >> 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 > > Nothing. Say Nothing! They have eyes and ears everywhere! > >> 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. > > The JPA TCK has not yet arrived at Apache, but once it does, those > of us who have gotten the secret handshake from Geir will be able > to run the TCK. But I agree with you, it is unclear how much > information we can divulge about what works and what doesn't. > > I'd suggest that to start, all JPA TCK test failures should be > analyzed and a small test case be developed to demonstrate the > problem. Then, the issue can be logged and tracked in JIRA. Without > jeopardizing confidentiality, the community can be involved in > fixing the issues. > > By the way, we should have a place to put new unit tests that fail. > We don't want them in the main line, because then the build is > broken. But we don't want them in JIRA issues either. Is there some > place that we could put tests that don't work yet? > > Craig >> >> -Patrick >> >> -- >> Patrick Linskey >> BEA Systems, Inc. >> >>> -----Original Message----- >>> From: Kevin Sutter [mailto:kwsutter@gmail.com] >>> Sent: Thursday, July 27, 2006 7:30 AM >>> To: open-jpa-dev@incubator.apache.org >>> Subject: State of OpenJPA code drop >>> >>> Hi Patrick, >>> Now that the code drops seem to be slowing down a bit, I'm >>> wondering whether you can give me an update on the >>> "completeness" of the OpenJPA code repository. I'm >>> attempting to verify some of the expected functionality and >>> I'm failing a few test scenarios. I'm just wondering whether >>> the majority of the code has now been dropped, and whether we >>> can start to post questions and/or bug reports. But, if >>> there's more to come, then I'd like to understand the state >>> of the repository. >>> >>> For example, is the OpenJPA JPQL query engine complete? I'm >>> hitting some failures with query statement parsing, type >>> conversions, database pushdowns, etc. Before posting more >>> detailed information about these failures, I'm wondering >>> whether it's complete yet or not. >>> >>> Related to this is the execution of the CTS OpenJPA TCK. It >>> looks like some basic problems with getting the dynamic >>> runtime class enhancer to work properly. Here again, not >>> sure if this is a configuration problem, or insufficient code >>> drop, or real problems. Do you have any personal experience >>> with executing the TCK that you could share? >>> >>> Thanks for your help! >>> >>> Kevin >>> >> _____________________________________________________________________ >> __ >> 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. > > Craig Russell > Architect, Sun Java Enterprise System http://java.sun.com/products/jdo > 408 276-5638 mailto:Craig.Russell@sun.com > P.S. A good JDO? O, Gasp! >