Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 324938 - Exceptions raised by EMF Compare, was working fine with Eclipse3.5
Summary: Exceptions raised by EMF Compare, was working fine with Eclipse3.5
Status: CLOSED INVALID
Alias: None
Product: EMFCompare
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows Server 2003
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: EMF Compare CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-10 05:49 EDT by Rahul Yadav CLA
Modified: 2011-06-14 11:22 EDT (History)
1 user (show)

See Also:

Attachments
Compare two diagrams on launching compare we will get NPE. (8.96 KB, text/plain)
2010-09-10 05:53 EDT, Rahul Yadav CLA 		no flags Details
Case 2. Expand the Differences tree, at leaf level of tree NPE will be thrown. (5.21 KB, text/plain)
2010-09-10 05:54 EDT, Rahul Yadav CLA 		no flags Details
View All 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 Rahul Yadav CLA 2010-09-10 05:49:59 EDT 
Build Identifier: Version: 3.6.0.v20100525-7b7mFKtFEx2XmfZ4_B7NUJA, Build id: I20100608-0911

We are using EMF Compare modules to compare our diagram files, for this we have written our own plug-in using EMF Compare APIs. We have our product running on Eclipse3.5 build id: I20090611-1540 and now migrating it to Eclipse3.6 for next release. The Diagram Comparator that was working fine with Eclipse3.5 is throwing NPE and other 
exceptions in Eclipse3.6 .

We encoutered these exception in atleast 2 cases in our scenario...

Case 1. Create a document variable in .diagram file, now compare two diagrams on 
        launching compare we will get NPE.
Case 2. Create diagram files, do not add any new components and now compare 
        them.Expand the Differences tree, at leaf level of tree NPE will be   
        thrown.

In case i replace Eclipse3.6 EMF Compare p[lug-in jars with EMF Compare jars from Eclipse3.5 and update my manifest.mf i do not see these exception.
Which give me the impression that issue is due to EMF Compare shipped with Eclipse3.6.

Let me know if you need more information on this.

Attached are the stacktrace for Case1 and Case2.

Reproducible: Always
Comment 1 Rahul Yadav CLA 2010-09-10 05:53:24 EDT 
Created attachment 178599 [details]
Compare two diagrams on launching compare we will get NPE.
Comment 2 Rahul Yadav CLA 2010-09-10 05:54:33 EDT 
Created attachment 178600 [details]
Case 2. Expand the Differences tree, at leaf level of tree NPE will be thrown.
Comment 3 Rahul Yadav CLA 2010-09-10 05:55:43 EDT 
I understand that trace is specific to our product but looking at stacktrace may give you some hints on where the problem may be.
Comment 4 Laurent Goubet CLA 2011-03-10 09:00:29 EST 
The first of these two is indeed EMF Compare failing ... in a way I cannot understand or reproduce : it would mean that a copied EObject would contain less elements that its original. If you still have models (and their metamodels) I can reproduce this with, please attach them to this bug.

As for the second, it comes from your item providers and I cannot help you with your code unless you attach a copy here (in which case I'll be able to tell you exactly which variable is "null" ... which won't help much as you can do that as well as I do :p).
Comment 5 Laurent Goubet CLA 2011-06-14 11:22:12 EDT 
Closing this as we have no way of reproducing the first exception, and the second isn't an EMF Compare issue.