[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2921?page=c... ] Gail Badner closed HHH-2921. ---------------------------- Assignee: Gail Badner Resolution: Rejected This is expected behavior due to Java limitations. Evicting the proxy for the superclass entity prior to executing polymorphic query will solve your problem. I've added test cases illustrating the expected behavior in org.hibernate.test.discriminator.DiscriminatorTest: - testLoadSuperclassProxyPolymorphicAccess illustrates that the polymorphic queries will return the proxy from the session cache; - testLoadSuperclassProxyEvictPolymorphicAccess illustrates that by evicting the proxy prior to executing the polymorphic queries, an instance of the subclass will be returned by the polymorphic queries. -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2921?page=c... ] Hung Tran Dinh commented on HHH-2921: ------------------------------------- I am running into the same issue, I disagree with Gail Badner. As I understand the bug, "Evicting the proxy for the superclass entity prior to executing polymorphic query will NOT solve the problem for sure". Evicting the proxy is easy, but it's really complexity to re-associate it with other existing entities in session. I totally agree with Johan, this code should be done at level of Hibernate. I don't know why this issue is rejected to fix. I suggest opening the issue again. -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira