Eclipse designer removes important attributes

[boris-petrov]

When saving a file, the Eclipse designer removes the following attributes from serviceTask nodes:

flowable:async="true" flowable:exclusive="false" flowable:class="MyClass"

The most important one being class. Then, when I run my project, it blows up with something like:

org.flowable.engine.common.api.FlowableException: Errors while parsing:                                                                                       
[Validation set: 'flowable-executable-process' | Problem: 'flowable-servicetask-missing-implementation'] : One of the attributes 'class', 'delegateExpression', 'type', 'operation', or 'expression' is mandatory on serviceTask. - [Extra info : processDefinitionId = myProcessDefinition | processDefinitionName = MyProcessDefinition |  | id = test |  | activityName = Test | ] ( line: 7, column: 5)

Original issue: flowable/flowable-engine#738

[JordanJordanov]

The same applies for flowable:inheritBusinessKey="true" in callActivity
<callActivity ... activiti:inheritBusinessKey="true"> is accepted but lost upon save
<callActivity ... flowable:inheritBusinessKey="true"> breaks the designer and the diagram is not shown

[Stexxen]

Just came across this problem. It effectively makes the Eclipse designer useless.
No commits since 2016, yet it's mentioned prominently in the docs.
If it's legacy then should be removed.

[paulhh]

We'd love a contribution to fix this - unfortunately, the core team doesn't have time to do it all :)

[pauldawg]

What is the best way to get my environment set up in Eclipse? I'd love to work on this, as well as an IntelliJ plugin :). I don't have any experience writing Eclipse plugins, but downloading and opening the project in Eclipse, I'm getting some missing resources trying to build it, so before I troubleshoot, I thought I would ask if you might have any suggestions to give me a jump start.