In Server. net 9.2, with the introduction of the multi-data source mode of arcgis server application, the arcgis server must provide some class libraries that support various data sources.. These class libraries are closely related to the controls provided in the adf, so they are frequently used during the development of arcgis server. The classes listed in the figure are all the classes that ArcGIS Server provides for us, Common APIs ESRI. ArcGIS. ADF. Web ESRI. ArcGIS. ADF. Web. DataSouces ESRI. ArcGIS. ADF. Web. Datasouces. ArcGISServer ESRI. ArcGIS. ADF. Web. DataSouces. ArcWebService ESRI. ArcGIS. ADF. Web. DataSouces. Graphics ESRI. ArcGIS. ADF. Web... DataSouces. IMS ESRI. ArcGIS. ADF. Web... DataSouces. OGCWMSService ESRI. ArcGIS. ADF. Web... UI. WebControls Specific APIs ESRI. ArcGIS. ADF ESRI. ArcGIS. ADF. ArcGISServer ESRI. ArcGIS. ADF. ArcGISServer. Editor ESRI. ArcGIS. ADF. ArcWebService ESRI. ArcGIS. ADF. IMS ESRI. ArcGIS. ADF. Connection ESRI. ArcGIS. ADF. Tasks All other class libraries except those listed above belong to Specific APIs. The Web ADF uses Common APIs to reach the corresponding Specific APIs. First, let's look at Common APIs: ESRI. ArcGIS. ADF. Web. DataSouces: contains various basic interfaces of Common APIs for various data sources, such as IGISDataSouce, IGISResouce, and IGISFunctionality. ESRI. arcGIS. ADF. web. datasouces. arcGISServer: the class is basically ESRI. arcGIS. ADF. web. an Implementation of interfaces in DataSouces. These classes are Common APIs for data sources such as ArcGIS Server in the web Adf. ESRI. arcGIS. ADF. web. dataSouces. arcWebService: the class is basically ESRI. arcGIS. ADF. web. an Implementation of the interface in DataSouces, including Common APIs for data sources such as ArcWebService in the web Adf. And so on. The class names in each database may be the same. For example, MapFunctionality ESRI. ArcGIS. ADF. Web. Datasouces. ArcGISServer ESRI. ArcGIS. ADF. Web. DataSouces. ArcWebService ESRI. ArcGIS. ADF. Web. DataSouces. Graphics ESRI. ArcGIS. ADF. Web... DataSouces. IMS ESRI. ArcGIS. ADF. Web... DataSouces. OGCWMSService Each database exists, but it targets different data sources. This is one of the manifestations of supporting multiple data sources and extending its own data sources. ESRI. ArcGIS. ADF. Web... UI. WebControls: contains various control classes provided by web adf for us. Let's take a look at Specifics APIs: The contents of various Specifics APIs libraries are clear and are special classes for different data sources. We can see from the name. For example, ESRI. ArcGIS. ADF. ArcGISServer is the Specific APIs for ArcGIS Server, Others and so on Starting with various controls and performing any operation, we first come into contact with these Common APIs, determine which data source is from the Common APIs, and then proceed to Specific APIs. Let's take a look at the following code: // Obtain the Functionality set from the control. IEnumerable funcenum = Map1.GetFunctionalities (); Foreach (IGISFunctionality gisfunc in funcenum) { // Layer name obtained from functionality IMapFunctionality mf = (IMapFunctionality) gisfunc; String [] layerids; String [] layernames; Mf. GetLayers (out layerids, out layernames ); // Obtain resource resources from functionality MapResourceLocal localRes = mf. Resource as MapResourceLocal; IMapServer pMapServer = localRes. MapServer; IMapServerObjects pMapServerObjects = pMapServer as IMapServerObjects; IFeatureLayer pFeatureLayer = pMapServerObjects. get_Layer (pMapServer. DefaultMapName, 0) as IFeatureLayer ;} First, obtain functionality from the control, and then obtain the resouce from functionality. Based on the resouce type, we know how to use specific APIs to change the resouce. In the above example, the Resouce type is MapResourceLocal, we can further use the Specific APIs-ArcObjects of MapResourceLocal. |