[mapguide-internals] RE: RFC 122 - Configurable CS Dictionary Paths

[Jackie Ng]

Hi Hugues,

There's an example of the logic I intend to port over here
(http://code.google.com/p/mg-desktop/source/browse/MgDesktop/System/PlatformInit.cpp).

That startup logic in turn was based on a code fragment that you yourself
posted 2 years ago:
http://osgeo-org.1803224.n2.nabble.com/Installer-progress-td2675328i20.html

The MgCoordinateSystemCatalog::SetDictionaryDir() API does successfully
change the dictionary path, but when this API was invoked, the library
status is not re-evaluated. So if this API was invoked with a library status
of lsInitializationFailed or lsLoadFailed, it stays that way even if the
path set (and the files within) check out, raising false flags for any code
that want to check the library status. Note that this library status check
is commented out in the above example.

I've made a patch for that here: http://trac.osgeo.org/mapguide/ticket/1821

The idea behind this RFC is to stick similar logic in the respective entry
points of the server (MgServer::open()) and web tier
(MgInitializeWebTier()), before anything else gets access to the
MgCoordinateSystemFactory

- Jackie

--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/RFC-122-Configurable-CS-Dictionary-Paths-tp6847435p6848204.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.