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: [jira] Updated: (OPENJPA-15) EJBQL grammar needs to be updated to
 relfect JPA specification
Date: Tue, 22 Aug 2006 14:25:57 -0700
Message-ID: <7D856CDFE035FF45A0420ACBD71BDD6301C75508@repbex02.amer.bea.com>
In-Reply-To: <89c0c52c0608221421uc019041ge7dfc521ba5a6b67@mail.gmail.com>
Thread-Topic: [jira] Updated: (OPENJPA-15) EJBQL grammar needs to be updated
 to relfect JPA specification
Thread-Index: AcbGMPH4Zu8G7UU6Sfep6SfyVwwomQAADa9w
From: "Patrick Linskey" <plinskey@bea.com>
To: <open-jpa-dev@incubator.apache.org>

(Note that my response here doesn't really answer your question.)

I think that it's good that we've been using JIRA to store information
about changes we're making, but I think it's far more important that we
create test cases that demonstrate the old bad behavior and assert the
new good behavior. That is, I'd like to see us create tests that fail
against the old version of OpenJPA but pass once the patch is applied.

One difficulty with this, of course, is that currently things are set up
so that all tests must pass during a normal compilation. Does anyone
know of a way to designate to mvn that certain tests are expected to
fail, so that we can commit tests that break along with JIRA reports?

-Patrick

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

> -----Original Message-----
> From: Kevin Sutter [mailto:kwsutter@gmail.com]=20
> Sent: Tuesday, August 22, 2006 2:21 PM
> To: open-jpa-dev@incubator.apache.org
> Subject: Re: [jira] Updated: (OPENJPA-15) EJBQL grammar needs=20
> to be updated to relfect JPA specification
>=20
> Now that we have successfully created a patch for OPENJPA-15,=20
> what is the
> process for getting this validated and hopefully accepted=20
> into SVN?  I have
> been able to verify that the patch can be applied, everything=20
> builds, and
> the existing testcases still work.  But, I'm not an expert=20
> with the code
> that is being updated, so it would be good for another=20
> committer to verify
> the changes.
>=20
> Thanks!
> Kevin
>=20
> On 8/22/06, Catalina Wei (JIRA) <jira@apache.org> wrote:
> >
> >      [ http://issues.apache.org/jira/browse/OPENJPA-15?page=3Dall ]
> >
> > Catalina Wei updated OPENJPA-15:
> > --------------------------------
> >
> >     Attachment: OPENJPA-15.openjpa-kernel.txt
> >
> > This patch is applied successfully against openjpa-kenel.
> > please ignore the previous attachments.
> >
> > > EJBQL grammar needs to be updated to relfect JPA specification
> > > --------------------------------------------------------------
> > >
> > >                 Key: OPENJPA-15
> > >                 URL:=20
> http://issues.apache.org/jira/browse/OPENJPA-15
> > >             Project: OpenJPA
> > >          Issue Type: Bug
> > >          Components: query
> > >            Reporter: David Wisneski
> > >         Assigned To: Catalina Wei
> > >         Attachments: OPENJPA-15.openjpa-kernel.txt, OPENJPA-15.txt
> > >
> > >
> > > when used in subquery, SELECT has different grammar than=20
> in top most
> > query.  SELECT NEW is not allowed.  FROM in subuqery has=20
> different syntax
> > than in top most query.  For example    "FROM d.employees as e " in
> > subquery where it would be invalid in top query.=20=20=20
> Expression syntax in
> > HAVING clause needs to allow  "HAVING min(e.salary) > 10 " is
> > valid  provided that e.salary is a grouping field.
> >
> > --
> > This message is automatically generated by JIRA.
> > -
> > If you think it was sent incorrectly contact one of the=20
> administrators:
> > http://issues.apache.org/jira/secure/Administrators.jspa
> > -
> > For more information on JIRA, see:=20
> http://www.atlassian.com/software/jira
> >
> >
> >
>=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.