Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Dali » Re: embedding JPQL in a typesafe manner
Re: embedding JPQL in a typesafe manner [message #610587] Fri, 04 July 2008 08:57
Miguel Garcia is currently offline Miguel GarciaFriend
Messages: 77
Registered: July 2009
Member
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
>
Previous Topic:embedding JPQL in a typesafe manner
Next Topic:Probem getting basic sample running
Goto Forum:
  


Current Time: Sun Nov 18 00:00:38 GMT 2018

Powered by FUDForum. Page generated in 0.01731 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top