Ahh, so you mean that in the filterXML -> filterImpl parser you've used "getDefaultGeometry()" or something to parse this filter correctly for *all* datastores...not just leaving it to each to decide?
How is this handled in SLD--where I leave the explicit geometry out of my rendering rules all the time? Any chance you can back-port your fix to 2.3.x, or tell me what class it was in so I can do so? thanks! --saul Justin Deoliveira wrote: > I just ran up against this in my wfs 1.1 work. And the answer i got from > the wfs spec gods is that if the only filter that is allowed to not > specify an attribute name is BBOX. All other filters must specify an > property name. > > Note however that on trunk this is fixed. A "null" property name is > interpreted as being the default geometry. > > -Justin > ------------------------------------------------------------------------- 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
