[
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.
Polymorphic query breaks if entity proxy already exists in session
------------------------------------------------------------------
Key: HHH-2921
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2921
Project: Hibernate3
Issue Type: Bug
Components: core
Affects Versions: 3.2.5
Environment: 3.2.5, PostgreSQL 8.1.2, jdk1.5.0_08, Windows XP
Reporter: Johan Hoogenboezem
Assignee: Gail Badner
I posted to the user forum about this on Oct 26
(
http://forum.hibernate.org/viewtopic.php?t=980752). I've had no reply. This is a
serious hassle for me, so I submit it as a bug.
--
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