GeoServer should double check all filter contents in GetFeature and Transaction
and report back meaningful error messages
-------------------------------------------------------------------------------------------------------------------------
Key: GEOS-2283
URL: http://jira.codehaus.org/browse/GEOS-2283
Project: GeoServer
Issue Type: Task
Components: WFS
Affects Versions: 1.7.0-RC4
Reporter: Andrea Aime
Assignee: Andrea Aime
Fix For: 1.7.1
Looking at GEOS-1673 you can find an example of an atrocious error message that
is the result of missing checks plus an invalid filter that compares an int
attribute with a string.
The same checks that are performed in GetFeature should be performed in the
Transaction elements that take a filter, and a check that makes sure filter
values are compatible with the attribute types should be added.
Two questions remain:
* where is the best place to store such a validation utility method? Or shall
we just create a few visitors and call them all replicating just the calls?
* is the proper behaviour to complain when a user sets a filter like
{{intAttribute = blabla}} or shall we just transform it into a Filter.EXCLUDE
and log the transformation with a warning?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-------------------------------------------------------------------------
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=/
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
