[fdo-trac] #208: GetSupportedCRSNames and GetFeatureClassStyles somtimes fail when FDO connection is created with configuration file

[FDO]

#208: GetSupportedCRSNames and GetFeatureClassStyles somtimes fail when FDO
connection is created with configuration file
-----------------------+----------------------------------------------------
   Reporter:  yangm    |       Owner:  yangm
       Type:  defect   |      Status:  new  
   Priority:  major    |   Milestone:  3.3.0
  Component:  FDO API  |     Version:  3.2.0
   Severity:  3        |    Keywords:       
External_id:           |  
-----------------------+----------------------------------------------------
 WMS provider used the physical mapping to return the referenced layer name
 pointed by feature class, because it considered one feature class may
 contains multiple WMS layers. It works for connecting a WMS server using a
 default schema mapping, which contains all layers from WMS server.

 But this defect happens when trying to use a configuration file to build
 up a FDO connection, but this configuration file only contained part of
 WMS layers (which are mapped by feature class). If user try to request one
 layer(pointed by one feature class) which is not contained in
 configuration file, but existed in WMS server. WMS provider cannot find
 the specific layer name because the old solution is based on the physical
 mapping.

 Since the default schema and schema mapping are built up on the rule: one
 WMS layer referenced to one feature class. So, we do not need to consider
 the multiple layers situation. We can use a existed naming dictionary
 between layer name and feature class name to check out any specific layer
 name pointed by WMS feature class.

-- 
Ticket URL: <http://trac.osgeo.org/fdo/ticket/208>
FDO <http://fdo.osgeo.org/>
Feature Data Objects