Legal to declare Signal with same name in different processes?

[joeysr20det]

I've run into an issue where I have created a workflow process the is composed of a Start Event Intermediate Throw Event and End Event. This process defines a Signal by the name testSignal and the Intermediate Throw Event throws this Signal.

Now in second process, I'm defining the a Signal with the same name testSignal and attempting to throw if from an Intermediate Throw Event in this second process.

The issue I'm running into, is when I deploy the second process (after the first has already been deployed), when the workflow engine is executing the process and gets to the Intermediate Throw Event, is ends with an exception saying Activiti has no behavior specified. Clearly looking at the XML it does have a Signal Event Definition specified and references the Signal defined in the XML file. However, if I simply change the name of the Signal to something else (i.e. testSignal1) I no longer run into this issue.

I'm pretty familiar with the BPMN 2.0 spec and Activiti. Looking over the spec and user guide I don't see anything saying you can't define a Signal (or any event for that matter) with the same name in different workflow processes. I'm I right here, or I have missed something?

Thanks

[trademak]

That should definitely work, but you should keep in mind that signals are defined at an Engine level. Could you create a unit test showing your issue?

Best regards,

[joeysr20det]

Here are two example processes that cause this issue. If you compare the two, you'll see that they only differ by process id and process name. Because both processes define a Signal name testSignal, the second process fails to execute and I get a message saying Activiti _43 has no behavior defined.

This issue was encountered on the Activiti 5.12 platform. Since a couple days ago when I posted this, I went ahead and upgraded to Activiti 5.15. This issue now seems to be resolved.

[jbarrez]

Ok, good to hear. There has been indeed been some work done in the signal-area.