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

Bug 386042

Summary: [UML Compare] The nested Compare Editor should allow to do comparison between an element owned by a resource and an element not owned in a resource
Product: [Modeling] Papyrus Reporter: Vincent Lorenzo <vincent.lorenzo>
Component: CoreAssignee: Vincent Lorenzo <vincent.lorenzo>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: arnaud.cuccuru, rschnekenburger
Version: unspecified   
Target Milestone: M7   
Hardware: All   
OS: All   
Whiteboard:
Bug Depends on: 385579    
Bug Blocks: 371606    

Description Vincent Lorenzo CLA 2012-07-26 09:24:49 EDT 
UML compare currently enables the comparison of two model elements. However, these two elements must belong to a resource. It would be useful to support the comparison of an element which belongs to a resource and another element which does not belong to a resource. The typical use case for that is the following: 
-	From a given object belonging to a resource, launch a transformation implying modification to this object
-	Resulting transformed object is computed, without being stored directly in the resource
-	Obtaining the resulting transformed object in the resource is done by comparing the original object (part of the resource) with the computed object (not part of the resource) using UMLCompare to evaluate differences, and validating (completely or partially) the transformation using merging facilities provided by compare.
Comment 1 Vincent Lorenzo CLA 2012-07-26 09:30:35 EDT 
R8482 : add tests to avoid null pointer with eobject.eResource() in order to support the case described in this bug
Comment 2 Vincent Lorenzo CLA 2012-07-26 09:34:52 EDT 
(In reply to comment #1)
> R8482 : add tests to avoid null pointer with eobject.eResource() in order to
> support the case described in this bug
 bad Revision number : this correct was done in R8629.
 
 R8630 : commit the JUnit test to verify that this kind of comparison works
Comment 3 Vincent Lorenzo CLA 2013-03-13 09:47:09 EDT 
This bug can be marked as resolved closed.