Hide Forgot
Description of problem: Signal event node shoul create a NodeTriggeredEvent when it is triggered by expected event. now it is triggered only when it has an incomming connection (which by documentation it should not have). Version-Release number of selected component (if applicable): BRMS-5.3.0.dev4 How reproducible: Every time Steps to Reproduce: 1. run attached reproducer 2. 3. Actual results: Start was triggered Gateway was triggered signal-incoming was triggered Gateway was triggered Gateway was triggered Gateway was triggered End was triggered Finished... Expected results: Start was triggered Gateway was triggered signal-incoming was triggered signal-no-incoming was triggered Gateway was triggered Gateway was triggered Gateway was triggered End was triggered Finished... Additional info:
I'm not sure this is a real issue, but rather a discussion about what it means to trigger a node. There are currently two types of node events, triggering (entering) a node and leaving a node. In the current implementation, catching intermediate events are not generating trigger events (they are only generating left events, as they are not really triggered, rather activated from outside). Similarly, throwing intermediate events are not generating left events (they are only generating triggered events, as they are not really left, as they have no outgoing connection). It would be possible to also generate both of these events for intermediate events, but since intermediate events don't have any real behaviour themselves, I'm not sure it would be useful to do so.
Could we decide whether this is actually on issue or not and if not, close the issue? I would recommend that the current implementation is what we believe should be the expected behaviour. If the user want to get an event when a signal node is triggered by an external event, he can use the nodeLeftEvent for that.
Thank you Kris for clarification. It sounds logical as you described. However, could it be added to documentation? Some generic information like "nodes without incoming connection do not generate NodeTriggeredEvent and nodes without outgoing connection do not generate NodeLeftEvent".
Updated in community docs: https://github.com/droolsjbpm/jbpm/commit/89bca815b8efc026dae51cd52afc0077a4f0eb71
Update status to ON_QA. Please verify them against ER6.