[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3409?page=c...
]
Manuel Dominguez Sarmiento commented on HHH-3409:
-------------------------------------------------
On further analysis, given that QueryKey precalculates its own hash code on construction,
and uses the customResultTransformer's hashCode as part of the calculation, the only
feasible solution is to have a stable hashCode() implementation for all ResultTransformer
implementations. The current design inherits hashCode() from Object, and since the
resulting hash is a function of the object's memory address, there is no way hash
codes will ever match in different JVMs.
ResultTransformers need smarter equals() and hashCode() impls
-------------------------------------------------------------
Key: HHH-3409
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3409
Project: Hibernate3
Issue Type: Bug
Components: query-criteria, query-hql
Affects Versions: 3.2.6, 3.3.0.CR1
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Fix For: 3.2.x, 3.3.0.CR2
Specifically, we need to account for the possibility of distributed query caching
considering that the ResultTransformer is part of the cached query key.
--
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