| Re: embedding JPQL in a typesafe manner [message #434918] |
Fri, 04 July 2008 04:57  |
Eclipse User |
|
|
|
Doug,
>I believe the best solution for development time checking of JPQL
>statements is through enhanced tooling.
That would indeed be the ideal solution. As far as I can see, the current
support (as of March 2008) for JPQL completion and validation is discussed
at
http://dev.eclipse.org/mhonarc/lists/dali-dev/msg00590.html
I'll check more regularly the sources of Dali to make sure I don't miss any
developments around that. At this point, it's not obvious to me that (a)
below is easier than (b):
(a) provide a parser for JPQL in Dali (with error recovery),
customize JDT's Content Assist to react based on the partial concrete
syntax tree for JPQL being edited.
vs.
(b) provide a compilation participant to rule out those remaining cases
accepted by JDT type checking,
yet breaking the static semantics of JPQL + underlying DB schema
Both approaches can cope with Content Assist, and both have a hard time with
DB refactorings. Given that it's an open question which approach is more
effective (whatever that means), I guess both need to be further explored to
better understand their pros and cons. I'll explore the JPQL embedding
following the techniques described in http://bugs.eclipse.org/234003
Miguel
http://www.sts.tu-harburg.de/~mi.garcia/
----- Original Message -----
From: "Doug Clarke" <douglas.clarke@oracle.com>
Newsgroups: eclipse.rt.eclipselink
Sent: Thursday, July 03, 2008 12:34 PM
Subject: Re: embedding JPQL in a typesafe manner
>I believe the best solution for development time checking of JPQL
>statements is through enhanced tooling. I believe this is in the Dali
>project's future plans.
>
> In our classic API we have expressions which use a generic API to define
> queries. It still takes strings for the entity attribute names and will
> not report spelling mistakes until runtime.
>
> Doug
>
"Doug Clarke" <douglas.clarke@oracle.com> wrote in message
news:bc9515fe5c3d447ea49467323d9fb9d3$1@www.eclipse.org...
>I believe the best solution for development time checking of JPQL
>statements is through enhanced tooling. I believe this is in the Dali
>project's future plans.
>
> In our classic API we have expressions which use a generic API to define
> queries. It still takes strings for the entity attribute names and will
> not report spelling mistakes until runtime.
>
> Doug
>
|
|
|
|
|
| Re: embedding JPQL in a typesafe manner [message #434927 is a reply to message #434925] |
Tue, 08 July 2008 13:43  |
| Eclipse User |
|
|
|
Rakesh wrote:
> I've noticed that JPQL content assist, syntax highlighting, etc. are
> features planned in the JQT project (https://jpaquerytool.dev.java.net/).
> I am not affiliated to the JQT project, but it would be great if this
> project can be integrated in Dali.
The JQT project is currently LGPL, which is not compatible with the EPL
license according to the Eclipse Foundation. It would have been nice to
consider an integration, but I think license related issues would prevent
it.
We are meeting soon to discuss features for our next release. I will make
sure this topic is discussed. It would be great if we could find a
contributor for this functionality.
Neil
|
|
|
| Re: embedding JPQL in a typesafe manner [message #610606 is a reply to message #434918] |
Tue, 08 July 2008 10:36 |
| Eclipse User |
|
|
|
Miguel,
The Dali team is just starting the planning of their next release
functionality. You may want to participate in these discussions or get
more actively involved in the project. I see you have posted a similar
question to the Dali forum so you have the necessary links.
You may also be interested in tracking the definition of the JPA 2.0 API
for defining queries. The expert group has stated that they are defining
such an API. They are always looking for feedback and requirements to help
guide the evolution of the specification.
http://www.jcp.org/en/jsr/detail?id=317
Doug
|
|
|
|
| Re: embedding JPQL in a typesafe manner [message #610615 is a reply to message #434925] |
Tue, 08 July 2008 13:43 |
| Eclipse User |
|
|
|
Rakesh wrote:
> I've noticed that JPQL content assist, syntax highlighting, etc. are
> features planned in the JQT project (https://jpaquerytool.dev.java.net/).
> I am not affiliated to the JQT project, but it would be great if this
> project can be integrated in Dali.
The JQT project is currently LGPL, which is not compatible with the EPL
license according to the Eclipse Foundation. It would have been nice to
consider an integration, but I think license related issues would prevent
it.
We are meeting soon to discuss features for our next release. I will make
sure this topic is discussed. It would be great if we could find a
contributor for this functionality.
Neil
|
|
|
Powered by
FUDForum. Page generated in 0.14966 seconds
Home