> What would make more sense to me, if there is really just one function with a
> certain name, is:
>
> FilterFactory.functionName(String functionName)
>
> it's all you need to locate the function. That would require the caller to
> verify
> that the available arguments match the function arguments size, which, with
> Function returning FunctionName, is feasible. Or not?
That is just it; we are not performing a look up here; but instead creating an
object.
This is just confusing because what should be called FunctionType is called
FunctionName.
We have need of creating a FunctionName data structure, even if we don't have
an implementation for it, when we are creating a FilterCapabilities describing
functions available in a remote WFS.
FilterFactory is responsible for both creating Filters; and for creating these
FunctionName descriptions. The issue I am having is that the method does not
allow me to fully define the FunctionName description.
Jody
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
