Changes between Version 2 and Version 3 of MapGuideRfc157

Timestamp:

Apr 11, 2017, 6:44:41 AM (7 years ago)

Author:

jng

Comment:

--

MapGuideRfc157

@@ -8 +8 @@
 ||RFC Template Version||(1.0)||
 ||Submission Date||9 Feb 2017||
-||Last Modified||4 Apr 2017||
+||Last Modified||11 Apr 2017||
 ||Author||Jackie Ng||
-||RFC Status||draft||
-||Implementation Status||discussion||
+||RFC Status||Adopted||
+||Implementation Status||Pending||
 ||Proposed Milestone||3.3||
 ||Assigned PSC guide(s)||(when determined)||
@@ -156 +156 @@
 
 Community
+
+== Addendum, 11 April 2017 ==
+
+It has been discovered using {{{QueryFeatures}}}, that the {{{MgFeatureInformation}}} returned has a {{{MgSelection}}} that cannot be interrogated in detail (ie. {{{GetLayers}}} on this selection will throw)
+
+The reason is the selection object is "disconnected" in that it has no internal reference to the {{{MgMap}}} it was initialized from (due to the (de)serialization of the {{{MgFeatureInformation}}} from server to web tier). There is a method {{{SetMap}}} that allows one to "attach" the original {{{MgMap}}} instance to the selection so that methods like {{{GetLayers}}} will work again, but this method is not part of the public API.
+
+To enable the selection within a {{{MgFeatureInformation}}} to be interrogated, the {{{SetMap}}} method will be promoted to {{{EXTERNAL_API}}}