I believe it is because the MgFeatureReader now throws exceptions when accessing null values and that the http handler hasn't been updated to check for nulls first.
I've already made a ticket for this issue here: http://trac.osgeo.org/mapguide/ticket/708 - Jackie Carl wrote: > > I tried Services API 'SelectFeatures' of 'Feature' on > http://localhost/MapGuide/mapagent/index.html. > > fill the Resource id with a MS SQL Server 2008 feature source > the Class name with a table name > and left other field as default. > > the return is as follows: > > Value for Prj_SpatialData property is null. > Value for Prj_SpatialData property is null. Exception occurred in method > MgNullableProperty.CheckNull at line 73 in file > d:\buildforgeprojects\mapguide_open_source_v2.0\build_23.8\mgdev\common\foundation\Data/NullableProperty.cpp > > Prj_SpatialData is of nullable varchar(MAX) field. > > When I manually update Prj_SpatialData='', OK, no error messages shown. > > I tried several tables. Once one table contains a row with null field > value, the above message will be shown. > > It seems SelectFeatures can't accept the null field value. If so, is it a > bug? > ----- http://themapguyde.blogspot.com http://www.linkedin.com/in/jackieng -- View this message in context: http://www.nabble.com/Services-API%3A-%27SelectFeatures%27-can%27t-accept-null-properties--tp20057379p20059721.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
