eclipse-qvto / org.eclipse.qvto

Eclipse Public License 2.0
0 stars 0 forks source link

MdaException in QvtModule.checkModuleErrors #1001

Open eclipse-qvt-oml-bot opened 1 day ago

eclipse-qvt-oml-bot commented 1 day ago

| --- | --- | | Bugzilla Link | 525435 | | Status | UNCONFIRMED | | Importance | P3 normal | | Reported | Oct 02, 2017 04:41 EDT | | Modified | Oct 02, 2017 04:42 EDT | | Reporter | EPP Error Reports |

Description

The following problem was reported via the automated error reporting:

Message: Operational QVT Interpreter\ org.eclipse.m2m.internal.qvt.oml.common.MdaException: Failed to parse transformation '/de.fraunhofer.fokus.expresso.transformation/resource/qvto/main.qvto', 5 error(s) found. [Line 148: Cannot find operation (createControlFlow(ActivityNode, ActivityNode, Activity)) for the type (),Line 155: Cannot find operation (createObjectFlow(ForkNode, InputPin, Activity)) for the type (),Line 158: Cannot find operation (createControlFlow(SendSignalAction, CallBehaviorAction, Activity)) for the type (),Line 165: Cannot find operation (createControlFlow(ActivityNode, ActivityFinalNode, Activity)) for the type (),Line 308: Cannot find operation (createObjectFlow(OutputPin, InputPin, Activity)) for the type ()]\ at org.eclipse.m2m.internal.qvt.oml.runtime.project.QvtModule.checkModuleErrors(QvtModule.java:269)\ at org.eclipse.m2m.internal.qvt.oml.runtime.project.WorkspaceQvtModule.getModule(WorkspaceQvtModule.java:51)\ at org.eclipse.m2m.internal.qvt.oml.runtime.project.QvtInterpretedTransformation.hasEntryOperation(QvtInterpretedTransformation.java:142)\ at org.eclipse.m2m.internal.qvt.oml.runtime.project.TransformationUtil.isRunnable(TransformationUtil.java:80)\ at org.eclipse.m2m.internal.qvt.oml.runtime.launch.QvtValidator.validateTransformation(QvtValidator.java:57)\ at org.eclipse.m2m.internal.qvt.oml.runtime.launch.QvtLaunchConfigurationDelegateBase.validate(QvtLaunchConfigurationDelegateBase.java:78)\ at org.eclipse.m2m.internal.qvt.oml.runtime.launch.QvtLaunchConfigurationDelegate$1.run(QvtLaunchConfigurationDelegate.java:53)\ at org.eclipse.m2m.internal.qvt.oml.common.launch.SafeRunner$SameThreadRunner.run(SafeRunner.java:33)\ at org.eclipse.m2m.internal.qvt.oml.common.launch.SafeRunner$1.run(SafeRunner.java:26)\ at org.eclipse.m2m.internal.qvt.oml.common.launch.ShallowProcess.run(ShallowProcess.java:45)\ at org.eclipse.m2m.internal.qvt.oml.common.launch.ShallowProcess.run(ShallowProcess.java:36)\ at org.eclipse.m2m.internal.qvt.oml.runtime.launch.QvtLaunchConfigurationDelegate$3.run(QvtLaunchConfigurationDelegate.java:95)\ at java.lang.Thread.run(null:-1)

Bundles:\ | org.eclipse.m2m.qvt.oml.common | 3.7.0.v20170604-1316 | 3.7.0.v20170604-1316 |\ | org.eclipse.m2m.qvt.oml.runtime | 3.7.0.v20170604-1316 | 3.7.0.v20170604-1316 |

Operating Systems:\ | Windows | 10.0.0 | 10.0.0 |

The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/59ca178fe4b02aaf8b19cdcd for the latest data.

Thank you for your assistance.\ Your friendly error-reports-inbox.

Created on behalf of ed@xxxxxx.xxx

eclipse-qvt-oml-bot commented 1 day ago

By Ed Willink on Oct 02, 2017 04:42

This looks like bad user code provoking an excessive response.

The user should get a pop up or other report of the problem.

It should not contribute to the error log / AERI.