-What steps will reproduce the problem?
1. In BPMN diagram/process create two or more signal events.
2. Define them same THE SAME Signalname.
3. One intermediate catching event. Others with the sames Signalname's -
throwing events.
-What is the expected output?
<signal id="sid-45968cfc-0105-465d-837c-0ff504225c78" name="Signal1"/>
<process id="Proc21" isExecutable="false">
....
<intermediateCatchEvent ...>
...
<signalEventDefinition id="sid-d24d56a2-b5dd-44ef-8687-8c2b6925df2e" signalRef="sid-45968cfc-0105-465d-837c-0ff504225c78"/>
</intermediateCatchEvent>
...
<boundaryEvent ... >
...
<signalEventDefinition id="sid-b7d506f1-1fa0-45e0-b379-62095dc41f62" signalRef="sid-45968cfc-0105-465d-837c-0ff504225c78"/>
</boundaryEvent>
</process >
-What do you see instead?
<signal id="sid-45968cfc-0105-465d-837c-0ff504225c78" name="Signal1"/>
<signal id="sid-270e32d3-ee90-4a34-a5a0-57a271819962" name="Signal1"/>
<process id="Proc21" isExecutable="false">
....
<intermediateCatchEvent ...>
...
<signalEventDefinition id="sid-d24d56a2-b5dd-44ef-8687-8c2b6925df2e" signalRef="sid-45968cfc-0105-465d-837c-0ff504225c78"/>
</intermediateCatchEvent>
...
<boundaryEvent ... >
...
<signalEventDefinition id="sid-b7d506f1-1fa0-45e0-b379-62095dc41f62" signalRef="sid-270e32d3-ee90-4a34-a5a0-57a271819962"/>
</boundaryEvent>
</process >
-What version of the product are you using? On what operating system?
last trunk
-Please provide any additional information below.
As I understand Signal names should be unique in processes deployment. How to
solve these problems.
Original issue reported on code.google.com by Mindauga...@gmail.com on 3 Aug 2012 at 5:37
Original issue reported on code.google.com by
Mindauga...@gmail.com
on 3 Aug 2012 at 5:37