It is a good critique! Indeed if I was doing the code review there would only be the two ways .. :-) - the query based approach; ie make a function and evaluate it on the collection - the object oriented approach; for when you want to hack a bit more
The mess of confusion left open by having the Collection_MaxFunction left as public visible; with a static final utility method around does nobody any favours. The Function implementation should all be package visible and only available through the factory. I will make a note of this as some technical debt for a rainy day. Jody > Thanx Jody, I'll try one of the options you listed. If I may, a bit of a > critique: it seems like in many instances > when working with the geotools library there's is more than one way of doing > things. I find this rather confusing, > rather than helpful. > Gaby > > > > > ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Geotools-gt2-users mailing list Geotools-gt2-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users