.Net API for MapGuide 1.2 Beta2 cannot access layers

[ksgeograf]

using the following code:

        MgSiteConnection con = new MgSiteConnection();
        con.Open(new MgUserInformation(sessionID));

        //get the map
        MgSite site = con.GetSite();
        MgResourceService rs = (MgResourceService)con.CreateService(MgServiceType.ResourceService);
        MgResourceIdentifier mapID = new MgResourceIdentifier("Session:" + sessionID + "//" + mapName + "." + MgResourceType.Map);
        MgMap map = new MgMap();
        map.Open(rs, mapID);

        //get a feature service
        MgFeatureService ftr = (MgFeatureService)con.CreateService(MgServiceType.FeatureService);

        MgLayerCollection colLayers = map.GetLayers();

The last line gives the following exception:

OSGeo.MapGuide.MgInvalidOperationException: The requested operation is invalid. 
- MgMapBase.GetLayers line 117 file 
c:\build_bond_area\mapguide_open_source_v1.2\build_13.7\mgdev\common\platformbase\MapLayer/MapBase.cpp 
- MgMap.UnpackLayersAndGroups line 640 file 
c:\build_bond_area\mapguide_open_source_v1.2\build_13.7\mgdev\common\mapguidecommon\MapLayer/Map.cpp 
--- End of inner exception stack trace ---

[ksgeograf]

changing a few lines fixes the problem:

from

MgResourceIdentifier mapID = new MgResourceIdentifier("Session:" + sessionID + "//" + mapName + "." + MgResourceType.Map);
MgMap map = new MgMap();
map.Open(rs, mapID);

to

MgMap map = new MgMap(con);
map.Open(mapName);

Perhaps the "old" way of opening a runtime map should just be removed?

[trevorwekel]

It's good that a workaround is available but the "old" way of opening a map should still work. The intent was to leave the existing API intact and deprecate it in the next release. This bug breaks existing scripts and should be investigated and fixed it possible.

[ksgeograf]

I tested some more, and it seems that opening the map with the following code:

MgMap map = new MgMap();
map.Open(rs, new ResourceIdentifier(...));

will cause the mentioned exception, when calling GetLayers()

Using this code instead:

MgMap map = new MgMap();
map.Open(rs, "Map1");

Will not cause the exception. This is the reason everything works fine with the .Net viewer. So, some problem exists in reading/unpacking layers from a map that was opened, using a resource identifier.

[ksgeograf]

It appears that the exception is caused by the map not having the associated ResourceService, even though the map was opened with that.

As far as I can see, the call bypasses the MgMap::Open, and calls MgResource::Open directly. This makes the the map miss the call to InitializeResourceService(resourceService). Not sure how to fix it though. Would it be sufficient to add the method to MgMap? Would that be picked up by SWIG?

[jbirch]

Has this been addressed? If not, is it worth addressing a deprecated method that does not work?

[jbirch]

Old ticket; closing. If still a concern, please retest at version 2.1 and re-open.