Description of problem: When calling signalEvent command, the process does not receive it. Please see the attached maven project with reproducer for details. Version-Release number of selected component (if applicable): BPMS 6.0.1.ER2 This is a regression, as it worked with 6.0.1 ER1. How reproducible: Please run mvn clean test on the attached maven project. Actual results: The test case fails. Expected results: The test passes.
Created attachment 870485 [details] Maven project with reproducer
Sorry, linked the tickets by mistake.
Marek, looking at the process it is actually not valid according to BPMN2 specification. We had recently made a fix to make it more accurate in terms of compliance with BPMN2 and that's why it now is failing on this process. extract from BPMN2 about intermediate events: " If the Intermediate Event is used within normal flow: -Intermediate Events MUST be a target of a Sequence Flow. Note – this is a change from BPMN 1.2 semantics, which allowed some Intermediate Events to not have an incoming Sequence Flow. " So although the engine works properly it lacks meaningful validation to warn the user about incorrect usage scenario. So this requires enhancement in validation so it won't be possible to be built with such constructs.
validation added so user will be warned early (on build time) that such construct is not allowed. jbpm master: https://github.com/droolsjbpm/jbpm/commit/36d427fef0917b6d9e30ae83213f6533016afb9c 6.0.x: https://github.com/droolsjbpm/jbpm/commit/e96b7ad547ac574261b8dc53fa7b447a5be17f3f
Verified in BPMS 6.0.2.ER2