[hibernate-issues] [Hibernate-JIRA] Created: (HHH-4714) JPQL fully qualified name for constructor instead of binary name

Maillefer Jean-David (JIRA) noreply at atlassian.com
Thu Dec 17 12:17:29 EST 2009


JPQL fully qualified name for constructor instead of binary name
----------------------------------------------------------------

                 Key: HHH-4714
                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4714
             Project: Hibernate Core
          Issue Type: Bug
    Affects Versions: 3.3.1
            Reporter: Maillefer Jean-David
            Priority: Minor


Constructor expression in JPQL NamedQuery should be fully qualified (EJB3.0 persistence spec, §4.8.2).
But if you have a nested class in the query, this doesn't work currently.

For example, if NestedA is a public static nested class in com.company.package.A, I have to write:
@NamedQuery(name="myquery", query="select new com.company.package.A.NestedA() from ...")
which doesn't work.

Using the binary name instead of the fully qualified name work:
@NamedQuery(name="myquery", query="select new com.company.package.A$NestedA() from ...")

Workaround (not standard compliant): use the binary name instead of the fully qualified name.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       



More information about the hibernate-issues mailing list