eclipse-qvt-oml-bot
commented
1 day ago By Ed Willink on Mar 04, 2019 09:00
(In reply to Christopher Gerking from comment #0)
An MdaException (which stands for what?)
MDA => Model Driven Architecture
This was an absolutely must-use buzz-acronym 10-20 years ago.
Nowadays it epitomizes the excessive hype.
--
Functionally folding into CoreException makes sense.
For compatibility, we perhaps have to worry about the 'instanceof' test that enables a QVTo failure to be distinguished from a platform failure.
--
It seems we don't actually understand its use so moving to a deprecated CoreException may be the way to go. But once I study MdaException a confused design; with / without IStatus.
For purely standalone usage, e.g. TransformationRunner.saveTraces there should be as little platform usage as possible. The origin ExtendedEmfUtil.saveModel does not use IStatus. This usage should not move to CoreException.
MdaException is internal permitting a total redesign, it is one of many QVTo de facto non-intrernals. Perhaps we need to partition the IStatus off in a new QVToCoreException leaving the IStatus part of MdaException deprecated.
| --- | --- | | Bugzilla Link | 486489 | | Status | NEW | | Importance | P3 normal | | Reported | Jan 25, 2016 11:18 EDT | | Modified | Mar 04, 2019 10:11 EDT | | See also | 537609 | | Reporter | Christopher Gerking |
Description
An MdaException (which stands for what?) encapsulates an IStatus. Therefore, it is sensible to replace it by CoreException (or at least subclass CoreException).