Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 332168 - [mwe2] [runtime] provide api to interrupt workflow execution
Summary: [mwe2] [runtime] provide api to interrupt workflow execution
Status: NEW
Alias: None
Product: EMFT
Classification: Modeling
Component: MWE (show other bugs)
Version: 2.0   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 enhancement with 1 vote (vote)
Target Milestone: SR1   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-08 15:15 EST by Knut Wannheden CLA
Modified: 2011-06-07 10:15 EDT (History)
3 users (show)

See Also:
sebastian.zarnekow: indigo+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Knut Wannheden CLA 2010-12-08 15:15:09 EST 
In MWE1 a workflow component could during its execution raise a WorkflowInterruptedException to signal that the workflow should be interrupted. This exception was then handled in WorkflowRunner by simply logging an error message (without exception stack trace).

I think it would make sense to add a corresponding API to MWE2.

Also note that the Xtext Generator class must also be extended accordingly so that a GeneratorFragment can throw this exception (unless Xtext introduces its own API for this purpose).
Comment 1 Henrik Rentz-Reichert CLA 2011-06-07 10:15:00 EDT 
I also would appreciate a possibility to interrupt the workflow without a stack trace being printed to the console.