When a layer filter fails layer should be rendered empty

[zspitzer]

currently when a layer filter fails, mapguide renders the layer without any filter see ticket:254

[zspitzer]

I think in terms of mapguide being developer friendly this is *really* important.

A use-case like a contractor assignment application where the contractor logs in and is meant to see their assigned jobs on the map (via a filter) can lead to some fairly serious business problems, lost time, two contractors turning up to the same job etc.

Any mapguide application which has completely separate customer business's cannot currently be guaranteed that their data is private.

I hit this error because the King.Oracle driver fails a lot with layer filters, but beyond monitoring SQL on the database there is no feedback, beyond maybe seeing too much data.

As an out of the box experience for someone evaluating mapguide, i would find this very frustrating and I did waste hours of time because of this myself

[jbirch]

Setting milestone to 2.0. Not a promise, just an indication of my support.

[tomfukushima]

This is as designed, but as I can see it is undesirable. Whoever does this, please change the behavior so that if the filter fails, the layer doesn't render and an entry is put into the error log. Tom

[ronnielouie]

Changed behaviour so that layer will not render when the filter fails. Instead an exception is thrown and written to log.

 http://trac.osgeo.org/mapguide/changeset/3152