Bug 379151 - NPE when in EvlMarkerResolutionGenerator#addResolution()
Summary: NPE when in EvlMarkerResolutionGenerator#addResolution()
Status: UNCONFIRMED
Alias: None
Product: Epsilon
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Dimitris Kolovos CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-10 11:31 EDT by Maarten Bezemer CLA
Modified: 2012-05-10 11:31 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 Maarten Bezemer CLA 2012-05-10 11:31:44 EDT 
Build Identifier: 

Sorry for all the reports, but I found another one...

EvlValidator#validate() adds possible fixes/resolutions to the EvlMarkerResolutionGenerator using the addResolution() method.
This method 'disconnects' the resolution after adding (not sure what that means).

The NullPointerException occurs when first the 'container' object is validated (and the resolution of the 'contained' object is added) and next the 'contained' object itself is validated.
Its resolution is added again (as it was not removed from EvlValidator#results?) but it got disconnected already (eg fix.getSelf() in addResolution() returns null)

I 'solved' this problem by adding a check whether fix.getSelf() returns null and just ignore if so (as the resolution already got added it does not seem to matter...)

Hopefully my description is clear enough, otherwise please let me know!

Reproducible: Always