Bug 1242410 - Default attribute in exclusive gateway lost during BPMN2 import
Summary: Default attribute in exclusive gateway lost during BPMN2 import
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Designer
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER1
: 6.2.0
Assignee: Tihomir Surdilovic
QA Contact: Jozef Marko
URL:
Whiteboard:
Depends On:
Blocks: 1242824
TreeView+ depends on / blocked
 
Reported: 2015-07-13 09:45 UTC by Martin Weiler
Modified: 2020-03-27 20:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1242824 (view as bug list)
Environment:
Last Closed: 2020-03-27 20:03:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Martin Weiler 2015-07-13 09:45:44 UTC
Description of problem:
After importing a process definition with an exclusive gateway, where one of the outgoing connections is marked as the default gateway, with no condition expression defined, the designer issues the following validation errors:

"Split node 'L4 Sending' [29] does not have a constraint for Connection L4 Sending [type=DROOLS_DEFAULT]" 

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create a new process in the business-central designer
2. Import the attached BPMN2 file

Actual results:
Designer reports validation errors.

Expected results:
No validation errors related to the exclusive gateway.

Additional info:

Exclusive gateway definition *BEFORE* the import:

    <bpmn2:exclusiveGateway id="_33DDA623-C86C-4B00-A90E-9B803D416D61" drools:bgcolor="#f0e68c" drools:selectable="true" drools:bordercolor="#FF6600" drools:dg="No : _49C48C17-F4B9-44EA-ABC4-F1A239057A84" name="L4 Sending" gatewayDirection="Diverging" default="_49C48C17-F4B9-44EA-ABC4-F1A239057A84">

<bpmn2:incoming>_5941FF39-76E0-44D0-BD62-98C782420CFA</bpmn2:incoming>

<bpmn2:outgoing>_B610EC4E-2A9A-4C6E-ACA9-09907F83EA81</bpmn2:outgoing>

<bpmn2:outgoing>_49C48C17-F4B9-44EA-ABC4-F1A239057A84</bpmn2:outgoing>
    </bpmn2:exclusiveGateway>

Note that the 'default' attribute contains the reference to one of the outgoing connections. 

Defintion *AFTER* the import (using view sources view):

    <bpmn2:exclusiveGateway id="_9B77EAFD-7EC6-44A6-99C3-7618750BD9ED" drools:bgcolor="#f0e68c" drools:selectable="true" drools:bordercolor="#FF6600" drools:dg="No : _49C48C17-F4B9-44EA-ABC4-F1A239057A84" name="L4 Sending" gatewayDirection="Diverging"> 

Note the missing 'default' attribute.

Comment 3 Tihomir Surdilovic 2015-07-13 17:54:50 UTC
Hi Martin, are you able to reproduce this problem on a smaller scale (small business process)? The attached one is fairly large and the issue is reproducible (but very hard to debug due to the size of the process).

I tried to reproduce this issue with a gateways with 1 incoming and 2 outgoing connections without success. Just wondering if you can.

Thanks.

Comment 4 Martin Weiler 2015-07-13 21:31:46 UTC
Hi Tiho, I failed to reproduce with the samples from the jBPM tests as well. If I manage to find a smaller/simpler process that shows the same problems, I will let you know.

Comment 5 Tihomir Surdilovic 2015-07-13 23:26:07 UTC
Was able to reproduce on small scale.
master commit: https://github.com/droolsjbpm/jbpm-designer/commit/253549601

Comment 7 Jozef Marko 2015-09-01 14:02:21 UTC
Attached process imported and attribute Default was preserved for exclusive gateways.


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