[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2m-atl-dev] Exception handling
|
(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
