Changes between Version 2 and Version 3 of MapGuideRfc182
- Timestamp:
- 08/06/20 05:03:22 (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MapGuideRfc182
v2 v3 9 9 ||RFC Template Version||(1.0)|| 10 10 ||Submission Date||4 Aug 2020|| 11 ||Last Modified|| ||11 ||Last Modified||6 Aug 2020|| 12 12 ||Author||Jackie Ng|| 13 13 ||RFC Status||draft|| 14 ||Implementation Status|| ||14 ||Implementation Status||Pending|| 15 15 ||Proposed Milestone||4.0|| 16 16 ||Assigned PSC guide(s)||(when determined)|| … … 24 24 == Overview == 25 25 26 This RFC proposes to add a new `MgInitializeLibrary` API for properly initializing the MapGuide APIwhen used in a class library context.26 This RFC proposes to add a new `MgInitializeLibrary` and `MgUnintializeLibrary` APIs for properly initializing and tearing down the MapGuide API respectively when used in a class library context. 27 27 28 28 == Motivation == … … 34 34 * `PlatformBase` (exposed to .net via the `OSGeo.MapGuide.PlatformBase.dll` assembly) 35 35 36 An example of this usage is FDO Toolbox, where this subset of the MapGuide API is used to provide coordinate system lookup and transfo mration services through the `MgCoordinateSystem` family of APIs.36 An example of this usage is FDO Toolbox, where this subset of the MapGuide API is used to provide coordinate system lookup and transformation services through the `MgCoordinateSystem` family of APIs. 37 37 38 38 However, usage of the MapGuide API in this context reveals a major teething issue around exceptions. Namely any exceptions thrown in this context will not have localizable error messages because the MapGuide API has not initialized with an appropriate string bundle. As a result, exceptions thrown from the MapGuide API in this particular context will not contain any useful error messages. … … 64 64 * `static void OSGeo.MapGuide.FoundationApi.MgUnitializeLibrary()` 65 65 66 This is already implemented in the [https://trac.osgeo.org/mapguide/browser/sandbox/jng/library_init library_init sandbox]. Upon adoption of this RFC, it will be merged into trunk. 67 66 68 == Implications == 67 69