Jody Garnett wrote: > A couple things; executing any sql function is not a good thing from a > security standpoint (but you know this).
Indeed. > You should be able to advertise > additional functions on a data store by datastore basis using the filter > capabilities data structure. You are the first person to want to do this > so please let me know if you have any questions. I had originally intended to use one dynamic proxy class for each function, because FilterCapabilities has a one-class to one-function mapping, but FunctionFinder wants a default constructor, and dynamic proxy classes constructors take an invocation handler. What I have done is to use a single RegisteredFunction class to handle all unrecognised functions. The design of FilterCapabilities does not support one class representing multiple functions. It needs to be refactored to have an instance (not a class) representing a function, and another instance representing a function with bound parameters. This would be much like the GeoAPI Attribute/Descriptor split. > I like your idea of storing the additional functions as a table; the > best move would be to have the PostGISDataStoreFactory check for this > table and make the correct implementations as needed. This functionality should be pulled right up into JDBCDataStore and friends. -- Ben Caradoc-Davies <[EMAIL PROTECTED]> Software Engineer, CSIRO Exploration and Mining Australian Resources Research Centre 26 Dick Perry Ave, Kensington WA 6151, Australia ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
