Bug 994408
| Summary: | jBPM engine does not support boundary event on Service Task | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Radovan Synek <rsynek> | ||||||||||||
| Component: | jBPM Core | Assignee: | Tihomir Surdilovic <tsurdilo> | ||||||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Radovan Synek <rsynek> | ||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||
| Priority: | medium | ||||||||||||||
| Version: | 6.0.0 | CC: | kverlaen, mbaluch, rzhang | ||||||||||||
| Target Milestone: | ER5 | ||||||||||||||
| Target Release: | 6.0.0 | ||||||||||||||
| Hardware: | Unspecified | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2014-08-06 20:10:16 UTC | Type: | Bug | ||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Embargoed: | |||||||||||||||
| Attachments: |
|
||||||||||||||
Created attachment 783741 [details]
script task process
Created attachment 783743 [details]
full stacktrace
Boundary events on nodes that aren't state-based is indeed not supported, since these nodes are executed immediately, so it's unlikely adding a boundary event would be useful. Would it be ok if we just prevent users from doing this then (or add validation messages) instead? The previous remark was for the script task only (where boundary events are not supported). Boundary events for service tasks should be, so will look into this. @Maciej, please take a look at the service task example, and if fixed assign to tiho for improving the validation in designer. service task does work as expected with boundary events. Script task as Kris described should not have boundary event attached as there will not be a way to call them. Transferring that to Tihomir to prevent adding boundary events on Script Tasks. Fixed in master and 6.0.x branch of designer - boundary events are no longer attachable to script tasks. I was able to import the definition (script task process attachment) where the script task has the boundary event without any validation error. I was also able to create the same definition in jBPM Designer - I managed to attach boundary event to script task without any problem and again - no validation error. Tiho, could you please provide the commit with the fix? It behaves like the fix wasn't included. Created attachment 805364 [details]
boundary on script task
Not sure what could be going on. I tested with 6.0.x and its fine (see attached png). Maybe try to clear your browser cache and test again. Let me know if issue is still there. Created attachment 805755 [details]
screenshot
Hello Tiho,
I cleared browser cache, also tried on different laptop - the behaviour is like this: boundary event cannot be attached when the event is being dragged from canvas. However, when I drag it directly from Object library panel to the script task, the boundary event can be attached.
could you please test again. i am not able to reproduce this issue. please try with latest. thanks Hi Tiho, I retested with org.kie:kie-wb-distribution-wars:6.0.0.Final:eap-6_1, is it the latest version you mentioned? I saw the same issue - boundary event can be attached on script task when it has been dragged directly from Object Library panel. fixed in designer master and 6.0.x branches Verified on BPMS-6.0.0.ER5 qe_test_coverage:covered by community unit tests |
Created attachment 783739 [details] service task process Take a look at attached process definitions - simple scenario with script task or service task. Both definitions were validated in jBPM Designer, but engine throws an exception when trying to build these definitions: java.lang.IllegalArgumentException: Boundary events are supported only on StateBasedNode, found node: org.jbpm.workflow.core.node.ActionNode (attaching full stacktrace) These are valid bpmn2 definitions. version: community 6.0.0.CR1