[mapguide-internals] Re: RFC91 Mapguide Error Codes

[Zac Spitzer]

is it feasible to include the new method in 2.2? otherwise if we just
edit the resources file
we could just return the existing string with an error code prefix (see below)

I guess for the FDO ones, we would need FDO to adopt this as well
and then just pass thru FDO error codes?

also how do we propose to add them into
http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Common/MapGuideCommon/Resources/mapguide_en.res

adopt a string format like

MgClassNotFoundException                              = MG-S-001: The
specified class was not found.

anyone across what do other projects do?


On 9 April 2010 14:04, Trevor Wekel <trevor_wekel at otxsystems.com> wrote:
> Yes.  I think it makes sense to have the property in MgException.
>
> Regards,
> Trevor
>
>
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Jackie Ng
> Sent: April 8, 2010 7:47 PM
> To: mapguide-internals at lists.osgeo.org
> Subject: [mapguide-internals] Re: RFC91 Mapguide Error Codes
>
>
> Should MgException be modified to include an error code property? Or only for
> certain subclasses?
>
> - Jackie
> --
> View this message in context: http://n2.nabble.com/RFC91-Mapguide-Error-Codes-tp4874857p4874893.html
> Sent from the MapGuide Internals mailing list archive at Nabble.com.
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>
>
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>
>



-- 
Zac Spitzer
Solution Architect / Director
Ennoble Consultancy Australia
http://www.ennoble.com.au
http://zacster.blogspot.com
+61 405 847 168