Move or rename resource should avoid breaking links

[christinebao]

Currently if you move or rename a resource, the other resources referencing to it are not updated and can't find the new location of the resource, thus they will not work anymore. For example, if you move or rename a FeatureSource, the LayerDefinitions which reference to this FeatureSource are not updated to use the new FeatureSource URL, and thus fail to work properly. RFC 74 overloads the ResourceService API MoveResource by adding a new parameter "bool cascade" to indicate whether to update the referencing resources or not. The old API will continue to exist along with the new API to keep backwards compatibility.

Please refer to RFC ​http://trac.osgeo.org/mapguide/wiki/MapGuideRfc74 for detail.

[christinebao]

Attach patch ​https://trac.osgeo.org/mapguide/attachment/ticket/1076/AddMoveResourceAPI.patch.

This patch adds a new API: void MoveResource(MgResourceIdentifier* sourceResource, MgResourceIdentifier* destResource, bool overwrite, bool cascade). The last parameter “cascade” indicate whether the referencing resources should be updated or not.

[ksgeograf]

A minor performance improvement:

Change /ApplicationRepositoryManager.cpp line 491 to:

Ptr<MgStringCollection> referencingIds = NULL;

The referencingIds is assigned in line 495, and if not cascading, it is not accessed.

To clarify this, line 518 could be changed to: if(cascade && referencingIds != NULL && referencingIds->GetCount() != 0)

[christinebao]

Thanks for the comment. ​https://trac.osgeo.org/mapguide/attachment/ticket/1076/AddMoveResourceAPI.2.patch is updated.