[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
|
Re: [m2m-atl-dev] Exception handling
|
- From: "Frédéric Jouault" <frederic.jouault@xxxxxxxxxxxxxx>
- Date: Tue, 16 Oct 2007 02:07:43 -0500
- Delivered-to: m2m-atl-dev@eclipse.org
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=MtVv2OeNPtOXnSvSzYfvY19++5edkKR4dhy6VgpD8V0=; b=fke7Sx858+thKVT9h2Czn9brvUyuKmTo0vXm/+CrneW/UuujNljHebA5CJac9gakUTRskenC99w7aof0XEnaO77+90CvZoe6FND9GKQIO/GpR5nU+JvesOpysa0NnSqc0ANOWeGb16zFzrP+Fdp6JGG0vRiLxxOy+yOC+C1Rk04=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=Z3H3ib0nbwnfTpSPHBh1f3SXcqjsCPH75gKX+/Qm49+fC/s4x/JqwdIubevQibyno2IYIWFfHvJjQF1s8sfbzPJfEUvNnGZQrKQ1Tm7QaZ0dQ7wHEKixdxIqsxd5XWlnfJEUlxW3l2rXADHHmTJcFwAE3kOkkvYPrJNfEtqIk+U=
Hi Martin,
Error notification is usually performed using the Debugger interface:
http://wiki.eclipse.org/ATL_Developer_Doc#Debugger
You can define your own Debugger that logs the errors the way you want :-).
Best regards,
Frédéric
On 10/10/07, Martin J Bartlett <jbartle9@xxxxxxx> wrote:
> (reply to my own email - not good I know)
>
> Of course my quoted mlethod is invoked via
>
> org.eclipse.m2m.atl.drivers.emf4atl.ASMEMFModel.loadASMEMFModel
>
> which ALSO would trap any exception and log it!
>
>
> CSC Financial Services SAS
> Registered Office: 14 Place de la Coupole, Axe Liberté, 94220 Charenton Le
> Pont, France
> Registered in France: RCS Créteil B 323 127 332
>
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> This is a PRIVATE message. If you are not the intended recipient, please
> delete without copying and kindly advise us by e-mail of the mistake in
> delivery.
> NOTE: Regardless of content, this e-mail shall not operate to bind CSC to
> any order or other contract unless pursuant to explicit written agreement
> or government initiative expressly permitting the use of e-mail for such
> purpose.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>
>
>
>
> Martin J
> Bartlett/FSG/CSC@
> CSC To
> Sent by: M2M ATL Developer list
> m2m-atl-dev-bounc <m2m-atl-dev@xxxxxxxxxxx>
> es@xxxxxxxxxxx cc
>
> Subject
> 10/10/2007 15:00 [m2m-atl-dev] Exception handling
>
>
> Please respond to
> M2M ATL Developer
> list
> <m2m-atl-dev@ecli
> pse.org>
>
>
>
>
>
>
> One of the biggest issues we've come across in running ATL is that the
> methods we need to use to kick off transformations rarely throw exceptions
> - they simply catch them, log them and return (with null if a value is
> expected). For "upstream" classes (launchers for example) this really isn't
> acceptable - we need to know explicitly WHY something downstream failed and
> report it in our OWN framework and standards.
>
> Just a simple example: org.eclipse.m2m.atl.drivers.emf4atl.ASMEMFModel
> .loadASMEMFModel(String name, ASMEMFModel metamodel, URI uri, ModelLoader
> ml)
>
> (which, incidentally declares that it throws Exception but does not). That
> load could fail for a number of reasons - FileNotFound being one of the
> most common I would imagine. I want my calling method to simply propagate
> that exception up to ITS caller.
>
> What plans are there to improve this state of affairs?
>
> Martin
>
> CSC Financial Services SAS
> Registered Office: 14 Place de la Coupole, Axe Liberté, 94220 Charenton Le
> Pont, France
> Registered in France: RCS Créteil B 323 127 332
>
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>
> This is a PRIVATE message. If you are not the intended recipient, please
> delete without copying and kindly advise us by e-mail of the mistake in
> delivery.
> NOTE: Regardless of content, this e-mail shall not operate to bind CSC to
> any order or other contract unless pursuant to explicit written agreement
> or government initiative expressly permitting the use of e-mail for such
> purpose.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>
>
>
>
> _______________________________________________
> m2m-atl-dev mailing list
> m2m-atl-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2m-atl-dev
>
>
> _______________________________________________
> m2m-atl-dev mailing list
> m2m-atl-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2m-atl-dev
>