Bugs item #634362, was opened at 2002-11-06 11:55 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=634362&group_id=22866
Category: None Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Michael Lipp (mlipp) Assigned to: Nobody/Anonymous (nobody) Summary: Failure if EntityBean overrides hashCode Initial Comment: This is a follow on to #595738 which has not been fixed properly. The CachedConnectionManager uses an entity beans equals and hashCode method to manage EJB containers. This fails if the EJB itself overrides equals/hashCode (see #595738 for a detailed description). The proper solution to the problem are collection/map implementations that use == instead of equals and System.identityHashCode instead of hashCode. The class IdentityWrapper which now exists in 3.0.4 does not solve the problem. It still calls hashCode on the EJB and (as explained in the previous bug report) a an EJB's hashCode implementation may fail if the EJB is in the pooled state. Worse, the current implementation actually disables connection caching. As every object is wrapped with a new IdentityWrapper ("key = new IdentityWrapper(rawKey)"), the "stack.contains(key)" will *always* fail. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=634362&group_id=22866 ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development