exclusive gateway default flow not stored in xml

[tse]

Default-flow is never stored on exclusive gateway:

* Setting the sequence flows coming out from exclusive gateway, then setting the default flow does not set in xml definition any element/attribute corresponding to default flow.
* Setting default-flow never changes the xml.

Designer version: 5.11.2


*** Default flow does work on service tasks ***


No special test unit required. Add ex.gateway, set default flow - it simply never gets stored, nothing happens in xml.

[luka]

I have noticed the same problem (version 5.11.2). It caused a bit of grief as some tests were unexpectedly failing until I looked more closely at the actual xml generated by the designer.

Are there any plans to release a fix for this soon?

[bardioc]

I have noticed the same problem (version 5.11.2). It caused a bit of grief as some tests were unexpectedly failing until I looked more closely at the actual xml generated by the designer.

Are there any plans to release a fix for this soon?

Would you please be so kind to open a JIRA issue for that? I'll check into it afterwards.

Thanks,

Regards,

Heiko

[luka]

It appears one has already been created http://jira.codehaus.org/browse/ACT-1546. I will keep an eye on the progress. Thanks.

[vahidg]

This issue still exist when working with the Activity Modeler in Activity Explorer (activiti-5.16.4). So if the <code>default</code> attribute is already set on the <code>exclusiveGateway</code> and the XML is opened with the Activity Modeler and then saved, the <code>default</code> attribute is removed from the XML. Also the fact that one of the flows is the default is not displayed with the graphical notation on the diagram.

I couldn't find a JIRA issue for this on the new JIRA, but only https://activiti.atlassian.net/browse/ACT-281 which says the feature is implemented.

[vahidg]

I'm experiencing this issue in Activiti Modeler in Activit Explorer version 5.16.4. So if in the XML an <code>excusiveGateway</code> has the <code>default</code> attribute, upon making any change in the Modeler and saving, the default attribute is removed from the XML which is highly undesirable. I couldn't find an issue on this in the new JIRA on Atlassian…