Jody Garnett ha scritto: > The answer (apparently) to list each function with a "fallback value"; > please see the SE 1.1 specification for details. > So you would list all the possible functions; if the user tries to call > a function in a context where it can not be understood the fallback > value would be used. > > I am not saying this is a great solution; just the one developed by the > SE 1.1 spec.
Indeed it's an ugly one imho. It works sort of fine from the point of view of best effort, which is already part of SLD (think the list of Graphics that the implementation can use in order to deal with point symbolizing), but it seems no good for WFS filters usage and, for what it matters, for people posting a custom SLD to a WMS. How do you know if the function is supported or not, if the fallback value was used or not? You have to hand check the results, which is quite ugly (access to the logs is another option, but it's an option only someone administering the server can use). So I'd say, fallback value could be a way, but I would like the user to be able and decide whether he wants to shoot himself in the feet with this, or get back a hard exception instead. Maybe a hint for the filter factory? Suggestions welcomed. Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------- 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 Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
