Andrea Aime wrote: > And why in the world would be interested in doing so? > Functions seem to me something you evaluate in memory, or encode in > some native form using an encoder, just like other expressions > and filters. > Property extraction is different in that you have many property > concepts and many ways to extract them (simple against feature, > java bean properties, xpath lookups and whatnot). > I don't see the parallel, can you make me an example of how this > would be beneficial? The idea is to treat the Function expression as a data structure; and leave it up to the code that is going to execute the expression to hunt down the implementation as appropriate to the context.
We should be able to call some SQL functions supported by PostGIS; even if we do not have a Java implementation with an exactly matching name. Jody ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
