Hi Bruno, We try our best to retain backward compatibility, but in some cases it is just not possible. In this case the upgrade of PHP caused compilation errors because it had added a GetMessage method. The way we resolved this was to rename our GetMessage method to GetExceptionMethod. Unfortunately, you now have to pay the price for this change.
Tom -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Bruno Scott Sent: Friday, June 04, 2010 12:43 AM To: [email protected] Subject: [mapguide-users] Mapguide OpenSource 2.2 backward compatibility problem Hi All We have a quite big MGOS application deployed on hundreds of different clients Most of them use MGOS 2.1 or MGE 2010 SP1 Some of them still use MGOS 2.0/1.2 or MGE 2010 / 2009 They will migrate to MGOS 2.2 or MGE 2011 but this process takes time so our application have to live in a multi version MGOS/MGE. Now comes the problem with MGOS 2.2/MGE 2011 We use extensively the MgException::GetMessage() fonction this function does not exist anymore because it is replaced by GetExceptionMessage. ...stuff deleted... Thanks for your answer. Bruno by the way, it would have been a lot easier for us if would have kept the GetMessage function for backward compatibility -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/Mapguide-OpenSource-2-2-backward-compatibility-problem-tp5138292p5138292.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
