[ http://issues.apache.org/jira/browse/OPENJPA-31?page=all ]
Marc Prud'hommeaux resolved OPENJPA-31.
---------------------------------------
Resolution: Fixed
This should be fixed as of last week.
Note that there was also a workaround for the bug: the named native query would
have been found if some persistence operation had been performed on the
declaring class before the attempt was made to create the native query (e.g.,
em.find(ClassThatDeclaresNativeQuery.class, 1)).
In any case, it should be working now, so the workaround should not be
necessary.
> Named query with @NamedNativeQuery annotation does not work
> ------------------------------------------------------------
>
> Key: OPENJPA-31
> URL: http://issues.apache.org/jira/browse/OPENJPA-31
> Project: OpenJPA
> Issue Type: Bug
> Components: query
> Environment: IBM Thinkpad laptop, Windows XP/sp2, DB2 8.1.7, openjpa
> Reporter: Ahmad Nouri
> Priority: Blocker
> Attachments: NamedNativeQueryBug.txt
>
>
> Creating namedQuery with @namedNativeQuery using resultClass or
> SqlResultSetMapping caused mapping tool error and run-time exception. Details
> in Attachment.
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
