Bug 1090843

Summary: Error boundary event on service task has wrong attachedToRef identifier
Product: [Retired] JBoss BPMS Platform 6 Reporter: Ivo Bek <ibek>
Component: Eclipse ToolingAssignee: Kris Verlaenen <kverlaen>
Status: CLOSED EOL QA Contact: Marek Baluch <mbaluch>
Severity: high Docs Contact:
Priority: high    
Version: 6.0.2CC: kverlaen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 19:44:05 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:

Description Ivo Bek 2014-04-24 09:53:27 UTC
Description of problem:

If I attach an error boundary event to a service task, configure it, and run the process, I will get the following exception:

java.lang.IllegalArgumentException : Could not find node to attach to: bpmn20:ServiceTask_1]]

That's because BPMN Designer will generate the following element:

<bpmn2:boundaryEvent id="BoundaryEvent_1" name="Forbidden client error" attachedToRef="bpmn20:ServiceTask_1">

The attribute attachedToRef has to contain only "ServiceTask_1" without the prefix "bpmn20:".

This error can be only fixed manually in XML editor and every change in the process definition requires the fix of attachedToRef attribute.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 2 Robert (Bob) Brodt 2014-09-02 19:00:00 UTC
It looks like this is fixed - the attachedToRef QName is no longer qualified with a prefix.

Comment 3 Marek Baluch 2014-10-06 08:27:23 UTC
Verified on JBDSIS 8.0.0.Alpha2