Bug 803999 - Eclipse editor is not BPMN2 conformant
Eclipse editor is not BPMN2 conformant
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: Tooling (JBDS) (Show other bugs)
BRMS 5.3.0.GA
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: John Graham
Tomas Schlosser
Depends On:
  Show dependency treegraph
Reported: 2012-03-16 05:34 EDT by Tomas Schlosser
Modified: 2012-11-07 10:30 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-11-07 10:30:19 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tomas Schlosser 2012-03-16 05:34:29 EDT
Description of problem:
BPMN2 specifies (among other things) how the nodes should be drawn. The editor in eclipse does not respect these requirements. This may cause confusion when customers come from Guvnor web-based editor to JBDS and vice versa.
Comment 1 Tomas Schlosser 2012-03-16 06:23:21 EDT
I created a list of problems following the BPMN2 specification:
* The marker for a Task that is a multi-instance MUST be a set of three vertical lines. (there is nothing in eclipse)
* A Business Rule Task is a rounded corner rectangle that MUST be drawn with a single thin line and includes a marker that distinguishes the shape from other Task types. (there is no mark in eclipse)

Also the markers are different (but I don't know whether that is a part of specification) - user task, script task, timer node, signal node.

Nodes that are not supported by eclipse editor are (naturally) not drawn correctly. This category contains (but is not limited to): different types of start/end/intermediate/boundary events, ad-hoc processes, swimlanes.
Comment 3 Kris Verlaenen 2012-11-07 10:30:19 EST
We're not planning to improve the "old" eclipse process editor (Drools Flow / RuleFlow) anymore and this will be addressed in the new Eclipse BPMN2 modeler.  So closing this one as won't fix.

Note You need to log in before you can comment on or make changes to this bug.