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

Bug 359373

Summary:	Type mismatch: cannot convert from null to boolean/int/long/float/double
Product:	z_Archived	Reporter:	pf yu <pfyu>
Component:	EDT	Assignee:	Project Inbox <edt.javagen-inbox>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	critical
Priority:	P3	CC:	jeffdouglas, jqian, mheitz, pfyu, svihovec
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description pf yu

2011-09-29 05:12:26 EDT

Build Identifier: 201109282102

Type mismatch: cannot convert from null to int/long

Reproducible: Always

Steps to Reproduce:
1. Check out project "org.eclipse.edt.eunit.test" from kan-cvs.
2. Add java generator to the project.
3. Clean the whole workspace.
4. Such errors exist in many places, for example:
fvt.librarysupport.TestMathLib2Lib

Comment 1 Matt Heitz

2011-09-29 10:18:19 EDT

This is a valid defect, but the testcases should be changed to avoid it.

The problem happens when null is passed as an argument to a function, and the function's parameter is not nullable.

For example, fvt.librarysupport.TestMathLib2LibtestStringAsInt4() contains this line
  LogResult.assertBigIntEqual1(null, nullableBigint);

And the first parameter of assertBigIntEqual1 is "expected bigint in".  Notice that it's not nullable.

In RBD you can pass null to a non-nullable parameter, and it's like passing in the variable's default value (zero, empty string, etc. depending on the parameter's type).  But in EDT if you assign null to a non-nullable variable, or pass null to a non-nullable parameter, we'll throw a NullValueException.  In other words, once the JavaGen error is fixed, this code won't work.

Comment 2 Jeff Douglas

2011-09-30 11:12:08 EDT

a different fix must have corrected this.

Comment 3 pf yu

2011-10-21 04:21:17 EDT

Verified in build 20111020