Morning Justin; we seem to be treading old ground[1] with your recent jira
issue:
http://jira.codehaus.org/browse/GEOT-3264
It seems I miss ready your patch; the interface you are proposing is here:
public interface FunctionFactory {
/**
* Returns the list of function names the factory provides.
*
* @return A list of function names, possibly empty, never null.
*/
List<FunctionName> getFunctionNames();
/**
* Returns a function with the specified name.
*
* @param name The name of the function
* @param args Variable list of expression arguments for the function.
* @param fallback A fallback literal to use in cases where the function
does not exist or
* can not be created. This argument may be {...@code null}.
*/
Function function(String name, List<Expression> args, Literal fallback);
}
Which is brilliant; for some reason I thought it was returning a List of
String; the fact that it returns a List of FunctionName is just great (and I
think has all the information I need).
Jody
[1]
http://osgeo-org.1803224.n2.nabble.com/GeoApi-Function-design-issue-td1959457.html#a1959461------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
