openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Craig L Russell <Craig.Russ...@Sun.COM>
Subject Re: State of OpenJPA code drop
Date Tue, 08 Aug 2006 21:44:54 GMT
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  
> 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?

> -Patrick
> -- 
> Patrick Linskey
> BEA Systems, Inc.
>> -----Original Message-----
>> From: Kevin Sutter []
>> Sent: Thursday, July 27, 2006 7:30 AM
>> To:
>> 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
408 276-5638
P.S. A good JDO? O, Gasp!

View raw message