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.
Jody Garnett wrote: > Sorry I thought that information was in the FilterCapabilities? Are we > using the FilterCapabilities information right now? If not can we? Note > that the way the OGC has defined this abstraction there each name > appears exactly once (with a known number of arguments). > > Cheers, > Jody >> How do you figure it is standing up ok? The api has no way of telling >> you how many arguments a function can take!! What is one supposed to >> do, start at 1 argument and see if that works, if an exception try 2, >> etc... >> >> Jody Garnett wrote: >>> I am less discouraged; the function api is standing up okay - it is >>> our implementation that is falling down. >>> Jody >>>> Well not really since its the original problem. I am a little >>>> discourages that the only resolution is to redesign the entire >>>> function api. >>>> >>>> Jody Garnett wrote: >>>>> That is hack 1 >>>>> >>>>> (Going to keep score) >>>>> >>>>> Jody >>>>>> So I guess I am stuck casting to Geotools implementation version . >>>>>> Sigh, so close to being fully against geoapi interfaces. >>>>>> >>>>>> Jody Garnett wrote: >>>>>>> Justin Deoliveira wrote: >>>>>>>> I agree Jody, this is a better design. But do we really need the >>>>>>>> new interface. And I don't mean can you think of hypothetical >>>>>>>> situations in which we could use it? I mean is there someone >>>>>>>> waiting on this issue and will be able to commit an >>>>>>>> implementation and use it within a few weeks. >>>>>>>> >>>>>>>> If the answer is no, I fear we are designing this for the sake >>>>>>>> of designing it. >>>>>>>> -Justin >>>>>>> So let's keep it in the bag for now; and set ourself a "pain >>>>>>> level" - ie if we start to see three hacks around the problem we >>>>>>> should do the real solution. >>>>>>> >>>>>>> Cheers, >>>>>>> Jody >>>>>>> >>>>>>> >>>>>>> >>>>> >>>>> ------------------------------------------------------------------------- >>>>> >>>>> 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 >>>>> >>>>> >>>>> >>>> >>> >>> >>> >> > > > ------------------------------------------------------------------------- > 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,45c95825213214820651628! > -- 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
