You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Albert Lee (Closed) (JIRA)" <ji...@apache.org> on 2012/02/02 18:16:53 UTC
[jira] [Closed] (OPENJPA-2065) JPA 2.0 Spec. Violation?
EntityManager#createNamedQuery(String, Class) bombs with non-entity Class
parameter
[ https://issues.apache.org/jira/browse/OPENJPA-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Albert Lee closed OPENJPA-2065.
-------------------------------
Close issue in preparation for 2.2.0 release.
> JPA 2.0 Spec. Violation? EntityManager#createNamedQuery(String, Class) bombs with non-entity Class parameter
> ------------------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-2065
> URL: https://issues.apache.org/jira/browse/OPENJPA-2065
> Project: OpenJPA
> Issue Type: Bug
> Components: jpa
> Affects Versions: 2.1.0, 2.1.1, 2.2.0
> Reporter: Laird Nelson
> Assignee: Rick Curtis
> Labels: specification
> Fix For: 2.2.0
>
>
> Suppose we have an interface, A.
> Suppose we have a JPA-compliant entity class, B, that implements A.
> This construction will fail at runtime:
> final TypedQuery<A> q = em.createNamedQuery("someNamedQuery", A.class);
> Hibernate and EclipseLink both accept this construction.
> I don't see anywhere in the JPA specification that the class parameter must denote an entity type.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira