Well...lemme think of a few pointers to offset the hashtable paradigm..in no particular order,
1. If the resultset returns too many results, there will be a memory constraint leading to automatic hashtable rehashing, which degrades performance.
2.Unlike the new collections framework, access to hashtables are synchronized. What this means is, if you are using
EJB framework then all the objects that are contained in hashtable have to be serializable.
3.If the resultset has int datatype you will have to create an Integer out of the int,every time u put or retrieve something from the Hashtable.
Since object creation is a costly process, any manager would agree to avoid this Integer object creation just for the purpose of putting things into the HashTable(Although there are workarounds to this by extending Hashtable class).
4.On the presentation front(JSP), while iterating thru the objects from the hashtable, you need to check whether an object is present thru .containsKey method to prevent java.lang.NullPointer exceptions..thereby adding to the load. Also one has to make sure that no null objects get added into the Hashtable(results again in the infamous Null Pointer exception).
Hope this gives u some moolah to be smarter
chz,
mpr
