Michael Bedward wrote: > Hi Andrea, > > Sorry, I didn't make myself clear. I meant that not having a fallback > value wouldn't be a problem. > > Thinking about it a bit more I don't really see how you could have a > type-safe fallback value anyway. For instance, you might use the env > function to store numbers and colours for a given SLD doc - a fallback > seems inappropriate in that case.
Well, we have converters, so type safe fallback does not seem an issue to me, we just try to convert to the target type? Also, the fallback is the users responsibility, if she puts a wrong value that's her fault. The reason I think that a fallback value is useful is that I want to use it to make parametrized SLD style sheets for WMS usage, where the env values would come from the request itself. So what if the request does not contain the env var values? The SLD designer can use the fallback value to give a reasonable behaviour in that case. Cheers andrea ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
