https://bz.apache.org/bugzilla/show_bug.cgi?id=62287
--- Comment #1 from Mark Thomas <ma...@apache.org> --- Given the current implementation, the odds of a hash collision look to be very small. The probably explains why the code has been like this since 6.0.x without any bugs reported. That said, the Javadoc for #hashCode() and equals() is clear that non-equal objects may have equal hash codes so checking equals in the event of equal hash codes looks like the safe thing to do. I'm assuming the #hashCode() was used for performance reasons. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
