|Re: [eclipselink-users] Cache issue with EclipseLink?|
Just to close the loop on this, the issue was indeed the hashCode's reference to other objects. Once we removed all the references to other objects within the hashCode method and just made it based on fields within the current object, everything started working fine. I'm not sure how many other people might run into this specific issue, but it's worth mentioning in your documentation somewhere since referring to other objects in a hashCode method doesn't violate any contracts and should be expected to work. Perhaps a "HashCode Recommendations" page should be added to the Wiki (if it doesn't already exist) that includes the information in your previous post since it was quite helpful. Thanks again for your assistance Kevin -- View this message in context: http://www.nabble.com/Cache-issue-with-EclipseLink--tp22440339p22745187.html Sent from the EclipseLink - Users mailing list archive at Nabble.com.
Back to the top