[
https://issues.apache.org/jira/browse/OPENJPA-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved OPENJPA-1291.
--------------------------------------
Resolution: Won't Fix
Closing as obsolete during backlog cleanup: The issue itself says trunk (2.0)
already gives a clear message and only asks for a backport to 1.2.x, a branch
that is long dead. Please reopen if this still happens with OpenJPA 4.x.
> 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 W. Sutter
> Priority: Major
>
> 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 was sent by Atlassian Jira
(v10.3.26#10030026)
