Bug 1011163

Summary: Cannot save process after an interface has been imported.
Product: [Retired] JBoss BPMS Platform 6 Reporter: Marek Baluch <mbaluch>
Component: Eclipse ToolingAssignee: Robert (Bob) Brodt <bbrodt>
Status: CLOSED CURRENTRELEASE QA Contact: Marek Baluch <mbaluch>
Severity: urgent Docs Contact:
Priority: high    
Version: 6.0.0CC: bbrodt, jomarko, kverlaen
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: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:
Attachments:
Description Flags
import java.util.Date conflicts none

Description Marek Baluch 2013-09-23 17:11:35 UTC
See linked issue.

Comment 1 Kris Verlaenen 2013-10-04 13:00:43 UTC
Linked Eclipse BZ marked as fixed

Comment 2 Marek Baluch 2013-12-10 17:18:18 UTC
Found a way to verify. Import of an interface is possible. Adding a new one using the '+' icon is not.

Comment 3 Marek Baluch 2013-12-10 17:19:30 UTC
Verified on JBTIS 4.1.3.CR1.

Comment 4 Jozef Marko 2015-02-12 06:55:29 UTC
Hi Bob, I am playing with importing interfaces a little bit and I have reproduced issue with overloaded methods with the same count of arguments, you have mentioned on eclipse bugzilla.

In the modeler BPMN2 Modeler 1.1.1.201501081320 conflicts are not resolved automatically. If user save file, there appears dialog, where user have to check which conflict will be resolved.

Is this desired behaviour? I am not claiming that this is bug. I am only asking, because I have had feeling from your comments, that conflicts are resolved automatically.

Comment 5 Jozef Marko 2015-02-12 06:57:59 UTC
Created attachment 990750 [details]
import java.util.Date conflicts

In this screenshot are showed conflicts, when user have imported java.util.Date.

Comment 6 Robert (Bob) Brodt 2015-02-23 14:50:42 UTC
Yes, the user's attention needs to be drawn to the fact that two or more elements have the same ID since IDs, by definition must be unique in the document. If these duplicate elements are referenced from other objects, those references should be checked to make sure they refer to the correct object(s) once the duplicate IDs are made unique by the editor.