Great idea. I am also planning on doing some caching based on query objects, and I hadn't realized that these weren't implemented.
In the meantime, I guess I can cache an Object that contains a Query, and traverse the query tree myself to implement missing .hashCode() or .equals() functionality. -Yonik On Thu, 10 Mar 2005 17:20:15 +0100, Bernhard Messer <[EMAIL PROTECTED]> wrote: > Hi, > > I would like to cache query objects in a hash map. My implementation > failed, because not all of the Query classes are implementing the > necessary method: "public int hashCode()". The same counts for the > "public boolean equals (Object o)", "public String toString(String > fieldName)" and "public String toString()". To force all subclasses of > Query to implement this 4 methods, i would like to make them abstract > within the base class and implement the missing ones in the subclasses. > So in Query class itself, it would look: > > public abstract String toString(String field); > public abstract String toString(); > public abstract int hashCode(); > public abstract boolean equals(Object o); > > I think this would make the API cleaner and more usable. > > Thoughts ??? > > Bernhard > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
