[mapguide-internals] RE: [fdo-internals] A note about
implementation of RFC 37 - Detailed Exceptions
traian.stanev at autodesk.com
Tue Aug 25 10:32:44 EDT 2009
Yes, we will have to drop the same part of the MapGuide RFC. As far as I know (I checked in Aleck's patch for RFC 79 yesterday), only the native error code is implemented in MapGuide as well.
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-
> bounces at lists.osgeo.org] On Behalf Of Trevor Wekel
> Sent: Tuesday, August 25, 2009 10:29 AM
> To: FDO Internals Mail List; MapGuide Internals Mail List
> Subject: [mapguide-internals] RE: [fdo-internals] A note about
> implementation of RFC 37 - Detailed Exceptions
> Hi Orest,
> There is a corresponding MapGuide RFC to expose the Detailed Fdo Exceptions
> through the MapGuide API http://trac.osgeo.org/mapguide/wiki/MapGuideRfc79.
> This work is being done by Autodesk. I do not know if there will be an
> impact on the MapGuide feature if the detailed exceptions are not exposed.
> I am cross posting to the MapGuide Internals list for clarification from the
> implementers of the MapGuide RFC.
> From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-
> bounces at lists.osgeo.org] On Behalf Of Orest Halustchak
> Sent: August 25, 2009 6:46 AM
> To: FDO Internals Mail List
> Subject: [fdo-internals] A note about implementation of RFC 37 - Detailed
> Regarding FDO RFC 37: http://trac.osgeo.org/fdo/wiki/FDORfc37
> The native error code part of this RFC will be done for FDO 3.5, but the
> additional detailed exceptions will be done for the release after this. Let
> me know if that will be a problem for anyone.
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
More information about the fdo-internals