Both of these Http requests will return one XML file which contains all feature information.
The parser to this XML is hard-coded in the file fdo_depot\Fdo\Unmanaged\Src\Fdo\Xml\FeaturePropertyReaderImpl?.cpp and it only accepts the name "featureMember".
This fix modified the code to handle both "featureMembers" and "featureMember" .
Fixed it in trunk stream with submission r6437 http://trac.osgeo.org/fdo/changeset/6437
This problem occurred from FDO 3.6 and there are two problems result in the failure of DigitalGlobel.
Http request " https://services.digitalglobe.com/catalogservice/wfsaccess?CONNECTID=7ae07ed7%2Dda2d%2D4d65%2Dac04%2D8220b20c1b93&version=1.1.0&service=WFS&REQUEST=GetFeature&TYPENAME=DigitalGlobe%3AImageInMosaicFeature" It is used in FDO 3.6 and 3.7. It returns one new XML element named as "featureMembers".
Http request " https://services.digitalglobe.com/catalogservice/wfsaccess?request=GetFeature&CONNECTID=7ae07ed7%2Dda2d%2D4d65%2Dac04%2D8220b20c1b93&version=1.0.0&service=WFS&REQUEST=GetFeature&TYPENAME=DigitalGlobe%3AImageInMosaicFeature" It is used in FDO 3.5. It returns the XML element "featureMember".
Both of these Http requests will return one XML file which contains all feature information. The parser to this XML is hard-coded in the file
fdo_depot\Fdo\Unmanaged\Src\Fdo\Xml\FeaturePropertyReaderImpl?.cpp and it only accepts the name "featureMember". This fix modified the code to handle both "featureMembers" and "featureMember" .
In FDO 3.6 and 3.7 the method "FdoWfsSchemaMerger::getXSDName" got the wrong result form URL " http://services.digitalglobe.com:80/wfsservice/schemas/gml/3.1.1/base/gml.xsd?CONNECTID=7ae07ed7-da2d-4d65-ac04-8220b20c1b93" The right result is "gml.xsd" instead of "gml.xsd?CONNECTID=7ae07ed7-da2d-4d65-ac04-8220b20c1b93".
This fix improved this parser to get the right XSD name. This problem hasn't occurred in FDO 3.5 for this code path hasn't been exercised in it.