eclipse-ocl-bot
commented
2 hours ago By Ed Willink on Nov 30, 2015 02:27
This appears to be a correct behaviour with an excessive diagnostic.
A user-defined operation invocation problem gives an OCL invalid result, and an explanatory error log message.
The Pivot-based OCL has a rich invalid that can carry the problem back to the caller.
Is there any alternative for the Classic Ecore-based OCL?
The current behaviour is particularly unhelpful to QVTo which already has a callOperation override. A better overrideable getInvalidResult(Exception) method?
It appears that the user method was identified but an NPE occurred before it was invoked. Probably source or arguments are null. A null source can certainly be invalid without error log. A probable fix for this case.
More generally, if a new EvaluationOptions.CACHE_INVALID option is set, any exceptions could be cached by the EvaluationEnvironment so that the invoking application (which sets EvaluationOptions.CACHE_INVALID) can access them on demand without troubling the error log.
| --- | --- | | Bugzilla Link | 483246 | | Status | RESOLVED FIXED | | Importance | P3 normal | | Reported | Nov 30, 2015 02:02 EDT | | Modified | Apr 08, 2019 10:47 EDT | | See also | Gerrit change https://git.eclipse.org/r/136876, Git commit 4cdba7f8, 546202 | | Reporter | EPP Error Reports |
Description
The following incident was reported via the automated error reporting:
\
General Information:
The following plug-ins were present on the execution stack (*):
Please note that:
Other Resources:
Thank you for your assistance.\ Your friendly error-reports-inbox.
This bug was created on behalf of ed@xxxxxxxxxxxx.