[mapguide-trac] #254: Failed Layer Filters should be logged to error.log

[MapGuide Open Source]

#254: Failed Layer Filters should be logged to error.log
------------------------------+---------------------------------------------
 Reporter:  zspitzer          |         Owner:        
     Type:  defect            |        Status:  new   
 Priority:  medium            |     Milestone:  2.0   
Component:  Resource Service  |       Version:  1.2.0 
 Severity:  major             |    Resolution:        
 Keywords:                    |   External_id:  963656
------------------------------+---------------------------------------------
Comment (by jbirch):

 I have seen this in the logs when testing the PostGIS provider without a
 user-defined filter.  This happened when we had a problem with the spatial
 filters not working and they were throwing exceptions.

 First MapGuide would try with the spatial filter exception thrown, then
 again (maybe with a different spatial filter?  Intersects instead of
 EnvelopeIntersects?  I'm a bit fuzzy on this now) and finally without any
 spatial filter at all.

 It seems to me that this behaviour is less desirable than determining if a
 provider supports that filter in it's capabilities, and then failing if
 the provider throws an exception.  The other case (silently getting
 everything) leads the user trying to figure out why their map is taking so
 bloody long to load :)

-- 
Ticket URL: <http://trac.osgeo.org/mapguide/ticket/254#comment:3>
MapGuide Open Source <http://mapguide.osgeo.org/>
MapGuide Open Source Internals