Bug 500651 - wrong name in calledElement reference after import via file system option
Summary: wrong name in calledElement reference after import via file system option
Status: NEW
Alias: None
Product: BPMN2Modeler
Classification: SOA
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows NT
: P3 normal (vote)
Target Milestone: future   Edit
Assignee: Robert Brodt CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-01 06:17 EDT by Peter Steinmetz CLA
Modified: 2016-09-01 06:40 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Steinmetz CLA 2016-09-01 06:17:30 EDT 
If you have a model "A" and rename it into "B", then import it via the file system option into another model C and set it as the called element of a CallActivity, the calledElement attribute is set as "ns:A". So instead of "ns:B", the old name is set here, whereas in the location of the import, the correct path with the new name ("something/something/something/B.bpmn") is set. Because of this, everytime you open model C, you get an UnresolvedReferenceException and the link from the CallActivity to model B is broken.
Comment 1 Robert Brodt CLA 2016-09-01 06:40:08 EDT 
Maintaining referential integrity is not an easy task and I have been putting this off for a long time. See bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=383849.