Better failure description for WFS service

[ksgeograf]

When a FeatureSource is exposed as WFS, it must function, otherwise the "GetCapabilitites" call fails. This should be fixed, and the error should be logged, and the feature removed from the GetCapabilitites response.

The currently logged message should be improved to include the resourceId of the failed featuresource. Currently I get this:

<2008-10-27T13:43:42> 		127.0.0.1	WfsUser
 Error: An exception occurred in FDO component.
        Connect failed: 
 StackTrace:
  - MgFeatureServiceHandler.ProcessOperation line 83 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_30.6\mgdev\server\src\services\feature\FeatureServiceHandler.cpp
  - MgOpDescribeSchema.Execute line 105 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_30.6\mgdev\server\src\services\feature\OpDescribeSchema.cpp
  - MgServerDescribeSchema.DescribeSchema line 545 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_30.6\mgdev\server\src\services\feature\ServerDescribeSchema.cpp
  - MgServerDescribeSchema.ExecuteDescribeSchema line 176 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_30.6\mgdev\server\src\services\feature\ServerDescribeSchema.cpp
  - MgFdoConnectionManager.Open line 858 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_30.6\mgdev\server\src\common\manager\FdoConnectionManager.cpp	An exception occurred in FDO component.
Connect failed: 

Seeing that I have +100 FeatureSources, and no idea which ones are exposed as WFS it will take half a day to find the culprit.

[jbirch]

Kenneth, if this is still a problem, please update version to 2.1.

[jng]

Fixed with changes for #2005