Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 343670 - Potential NPE in XbaseJavaValidator
Summary: Potential NPE in XbaseJavaValidator
Status: CLOSED WORKSFORME
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 2.0.0   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-22 16:21 EDT by Karsten Thoms CLA
Modified: 2017-09-19 17:51 EDT (History)
1 user (show)

See Also:

Attachments
Screenshot: Debugger (549.39 KB, image/png)
2011-04-22 16:21 EDT, Karsten Thoms 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 Karsten Thoms CLA 2011-04-22 16:21:59 EDT 
Created attachment 193946 [details]
Screenshot: Debugger

When cleaning my projects I run into a NPE in XbaseJavaValidator#checkInstantiationOfAbstractClass(). The XConstructorCallImplCustom#constructor reference is an unresolved proxy, so 
   constructorCall.getConstructor().getDeclaringType()
returns null.
Comment 1 Sven Efftinge CLA 2011-04-24 13:47:55 EDT 
NPEs are handled by the framework
Comment 2 Karsten Thoms CLA 2017-09-19 17:40:22 EDT 
Closing all bugs that were set to RESOLVED before Neon.0
Comment 3 Karsten Thoms CLA 2017-09-19 17:51:32 EDT 
Closing all bugs that were set to RESOLVED before Neon.0