Justin Deoliveira wrote: > Hmm, fair enough, if it is limiting it is limiting... but do you have > an example of where it is too limiting? The problem i am running up > against right now is when a "empty" property name is supplied as part > of binary spatial op. We had a choice between: - Expression.NULL (representing no expression provided by user so the system better do something) - encode default geometry; and xpath="", context=Geometry.class is the best we could come up with right?
Not sure which one of those you mean as "empty". > Now does this mean that we should get the "default geometry", or does > it mean we should get "all geometries". Geotools internally assumes > the former. We should be careful in what we assume, Expression.NULL is a better choice for storing the idea of a "default geometry" in an SLD (aka the SLD should store Expression.NULL and document it's own assumptions on how it wants that handled); but you did not want to create an additional PropertyAccessor method in order to capture that idea.... > So that leaves me doing a special case check, which would be easier > if the first expression was strongly typed. Expression.NULL is available; you are free to make the tradeoff the other way (just add the needed method to PropertyAccessor and make sure not to break the JPox spatial team). Cheers, Jody ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
