Understandable since it came after the fact. In my opinion its not ok, a function by itself is not self describing enough to create the FilterCapabilities in the first place!!
Jody Garnett wrote: > I see - so the GeoAPI Function API may be "okay", we just not have used > the full scope of the GeoAPI interfaces needed to define our problem? > > Sigh! > Jody >> Unfortunatley I have no way of generating a FilterCapabilities from >> the functions plugged in via factory api. And no we are not using >> FilterCapabilities right now. The only use of it I have seen is in >> Postgis to declare which functions it can encode as sql, which does >> not report the number of arguments. > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier. > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Geoapi-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/geoapi-devel > > !DSPAM:1004,45ca213126281425493344! > -- Justin Deoliveira [EMAIL PROTECTED] The Open Planning Project http://topp.openplans.org ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
