DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <https://issues.apache.org/bugzilla/show_bug.cgi?id=44059>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
https://issues.apache.org/bugzilla/show_bug.cgi?id=44059 ------- Additional Comments From [EMAIL PROTECTED] 2008-02-25 20:42 ------- I'm not sure. There are a great many more references to HashMaps in the 2.0 base than the one I fixed. This was the only one I saw giving me trouble, but only time will tell. The other alternative would be to change all HashMaps to Hashtables. I am not sure of the functional differences between the two objects, except that Hashtables are synchronized and don't accept nulls. I thought for the moment that synchronizing the HashMap was the best way to go. HashMaps should be quicker in a read environment, but apparently they don't always work amongst several threads. These problems definitely seem to be the same thing. 2.0 code base: 86 classes with HashMaps 1 class with Collections.synchronizedMap 1 class with Hashtable -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
