WFS: can't create layer against to the wfs feature source with multiple schemas

[hubu]

Steps:

1. Launch MG Studio.
2. Create one WFS connection

the first one in sample URLs ​http://frameworkwfs.usgs.gov/framework/wfs/wfs.cgi?DATASTORE=Framework

3. Create one layer based on the connection create in Step2.

Results: An exception thrown: ""Schema can not be found in the collection.""

Expected results: The layer could be created successfully.

[hubu]

This is actually a FDO issue. WFS only supports one "Real" schema. I can work out a workaround on MapGuide Server to avoid the exception throwing. The workaround is, before decribeschema, we don't set the classname/schemaname. If we set the schemaname before describeschema, the WFS provider will check whether the schemaname is the last one of schemacollection, if not the exception throws out. On the other hand, set the classname/schemaname is useless for MapGuide, the FDO still need to get all schemas from the server, and reture them to MapGuide Server. So set the schemaname doesn't improve the performance of MapGuide. I tested the fix against SDF/SHP/Orcale, it works fine for me.

[jbirch]

Appears to have been fixed in [5360]