openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Sutter (JIRA)" <j...@apache.org>
Subject [jira] Created: (OPENJPA-1291) Unhelpful exception message with badly formed jpql
Date Thu, 10 Sep 2009 19:26:58 GMT
Unhelpful exception message with badly formed jpql
--------------------------------------------------

                 Key: OPENJPA-1291
                 URL: https://issues.apache.org/jira/browse/OPENJPA-1291
             Project: OpenJPA
          Issue Type: Bug
          Components: query
    Affects Versions: 1.2.1
            Reporter: Kevin Sutter


http://n2.nabble.com/Unhelpful-exception-message-td3603002.html#a3603002

This discussion shows that a missing object reference in a jpql query sub-select produces
a cryptic exception message.  Pinaki has shown that the message is much clearer in trunk (2.0.x).
 If this new message processing is sufficient, then maybe this can be back ported to 1.2.x?
 But, maybe this new exception processing is dependent on the new sub-select processing architecture
that was developed as part of JPA 2.0.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message