Bug 1184422
Summary: | Escalation and Signal in process definitions cause validation errors | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Jozef Marko <jomarko> | ||||
Component: | Eclipse Tooling | Assignee: | Kris Verlaenen <kverlaen> | ||||
Status: | CLOSED EOL | QA Contact: | Jozef Marko <jomarko> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 6.1.0 | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2020-03-27 19:43:27 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: |
|
Description
Jozef Marko
2015-01-21 11:02:28 UTC
Fixed with Luna build 1.1.1.201501262023 Verified on BPMN2 Modeler 1.1.1.201501282123 Not included in jbds-8.0.2.GA_jbdsis-8.0.0.CR2. I have to reassign this issue. In jbds-8.1.0.CR1_jbdsis-8.0.1.CR1-BPMN2 Modeler 1.1.2.Final, if user want to use defined escalation or signal, attribute itemSubjectRef is missing in <dataInput> or <dataOutput> tag of given element. Error like "Data Input Signal_3_Input () has no Data Type" is displayed. See the attachment 'process with signal' on eclipse bugzilla. I have been investigating this issue a little bit more. I have prepared 4 processes with different kinds of escalation elements. In each process is declared variable 'escalationVariable' of type 'java.lang.RuntimeException'. Next in each process is declared escalation of name 'ExceptionEscalation' and code 'java.lang.RuntimeException' *** escalation_end.bpmn2 In (EscalationEnd) node is selected 'ExceptionEscalation' but no variable for mapping. If you check source view, there are two errors. 1. Data Input Escalation_2_Input () has no Data Type 2. Input to Escalation Event Definition defined in End Event is not mapped to a Source data item Please select 'escalationVariable' in 'Source' combobox in section 'Map Outgoing Escalation Data From'. Save file and check source view again. There will be still 1. error. *** escalation_boundary.bpmn2 In (EscalationBoundary) node is selected 'ExceptionEscalation' but no variable for mapping. If you check source view, there is one error. 1. Output from Escalation Event Definition is not mapped to a Target data item Please select 'escalationVariable' in 'Target' combobox in section 'Map Incoming Escalation Data To'. Save file and check source view again. Old error disappeared and new occured. 1. Data Output Escalation_2_Output () has no Data Type *** escalation_start.bpmn2 Completely the same situation as in escalation_boundary.bpmn2 *** escalation_throw.bpmn2 Here is the situation complicated a little bit more. In (ThrowEscalation) node is selected 'ExceptionEscalation' but no variable for mapping. If you check source view, there are two errors. 1. Data Input Escalation_1_Input () has no Data Type 2. Input to Escalation Event Definition defined in Intermediate Throw Event is not mapped to a Source data item If I select 'escalationVariable' in 'Source' combobox and 'java.lang.RuntimeException' for 'Data Type' in section (2), I fix both errors.. If I select 'escalationVariable' in 'Source' combobox in section (1), there will still remain 1. error. Created attachment 1010065 [details]
four variants of escalation processes
I believe this has been fixed with bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=463362 Can you please retest with version 1.1.4? Fix looks good for plain eclipse with BPMN2 Modeler 1.1.4.201506092231. I will definitely close this BZ when some jbdsis containing BPMN2 Modeler 1.1.4.* will be available. Verified on jbds-9.0.0.CR1_jbdsis-9.0.0.Alpha1. |