[
http://opensource.atlassian.com/projects/hibernate/browse/HSHARDS-51?page...
]
Max Ross commented on HSHARDS-51:
---------------------------------
I'm struggling to figure out what I meant with this bug. I don't see a class
called ShardResolutionStrategyImpl, and I don't see why implementations of
ShardResolutionStrategy would need equals() and hashCode() in order to implement a
cache-aware version since there would still only be one ShardResolutionStrategy - no need
to hash or compare multiple instances. My guess is that I was actually referring to
ShardResolutionStrategyDataImpl, to which I added hashCode() and equals() methods on Feb.
13. One _would_ need hashCode() and equals() to implement a cache-aware
ShardResolutionStrategy. I'm guessing I just got mixed up. Let me know if that makes
sense to you, and if so I'll mark this bug fixed.
Thanks!
Max
ShardResolutionStrategyImpl needs equals() and hashCode()
---------------------------------------------------------
Key: HSHARDS-51
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSHARDS-51
Project: Hibernate Shards
Issue Type: Bug
Components: engine
Reporter: Max Ross
Assignee: Max Ross
Priority: Minor
Fix For: 3.0.0
There's basically no way to implement a cache-aware ShardResolutionStrategy until we
implement equals() and hashCode() on ShardResolutionStrategyImpl.
--
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