Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 355648

Summary: Not able to set the calledElement property of Call Activity Node.
Product: [SOA] BPMN2Modeler Reporter: Robert Brodt <bbrodt>
Component: UIAssignee: Robert Brodt <bbrodt>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: jomarko
Version: 0.0.1   
Target Milestone: 0.0.1-M1   
Hardware: PC   
OS: Windows 7   
URL: https://issues.jboss.org/browse/JBPM-3154
Whiteboard:
Bug Depends on: 355631    
Bug Blocks:    
Attachments:
Description Flags
sample process none

Description Robert Brodt CLA 2011-08-24 06:16:35 EDT
Created attachment 202070 [details]
sample process

Add a CallActivity Node. Go to the properties panel and give some processId value to the calledElement property(other than the current process). This value is not getting persisted to the XML when i press the save button.

Also, if i directly give this processId(say com.sample.bpmn.hello) in XML file. I am getting the following error in my problems view of eclipse.

UnresolvedReferenceException: Unresolved reference 'com.sample.bpmn.hello'.
Comment 1 Brian Fitzpatrick CLA 2011-12-09 15:58:34 EST
We need to offer a way to handle this on the Call Activity property tab. Right now there isn't a way to set the called Element
Comment 2 Brian Fitzpatrick CLA 2011-12-15 14:22:28 EST
Ok. This is actually done. A couple of things to note.

1) The Call Activity in the attached file references the internal process by name and not by ID - thus the "UnresolvedReferenceException: Unresolved reference 'com.sample.bpmn.hello'." error.

2) Using the tweak I checked in for 355631, the Called Element Ref list populates the drop-down list with the internal Process (called "Process for Internal") and when selected seems to happily validate instead of getting the error in (1).
Comment 3 Jozef Marko CLA 2016-09-16 08:17:33 EDT
No more reproducible with  BPMN2 Modeler - 1.2.5.Final-v20160831-1132-B114