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 awhite@bea.com designates
 63.96.176.25 as permitted sender)
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <89c0c52c0608221439o7055c30fn10b1cf5f8a2d1a7c@mail.gmail.com>
References: <89c0c52c0608221421uc019041ge7dfc521ba5a6b67@mail.gmail.com>
 <7D856CDFE035FF45A0420ACBD71BDD6301C75508@repbex02.amer.bea.com>
 <89c0c52c0608221439o7055c30fn10b1cf5f8a2d1a7c@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <3E340C1F-6F37-4130-BDDF-76395F3A0894@bea.com>
Content-Transfer-Encoding: 7bit
From: Abe White <awhite@bea.com>
Subject: Re: [jira] Updated: (OPENJPA-15) EJBQL grammar needs to be updated to
 relfect JPA specification
Date: Tue, 22 Aug 2006 15:04:21 -0700
To: open-jpa-dev@incubator.apache.org

> Sounds like a good plan.  New or updated tests would be good to  
> demonstrate
> that a fix works.  Even if we would provide a working testcase with  
> the fix,
> that would be a good way to populate our test bucket.
>
> Concerning all of the query related JIRA reports that have been  
> opened, do
> we have a base set of testcases for query within OpenJPA?  That is,  
> do we
> have a query test framework that we should attempt to work within?

I also think that checking in a test case with any significant patch  
is critical.  (You might point out that I've been making a lot of  
commits, and I have not been committing test cases to go with them.   
But the test cases for my commits do exist... unfortunately as part  
of Kodo's test suite, which we have yet to migrate to OpenJPA.)

And no, we don't have a framework for query test cases (or even  
persistence-using cases in general) in OpenJPA right now.
_______________________________________________________________________
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.