Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 357229 - Nullable type not cleared in TypeBinding on reset
Summary: Nullable type not cleared in TypeBinding on reset
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Paul Harmon CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-09 09:15 EDT by Justin Spadea CLA
Modified: 2017-02-23 14:18 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Justin Spadea CLA 2011-09-09 09:15:21 EDT
When a binding for a nullable type is reset by the builder (via IPartBinding.clear()) the nullableType field of TypeBinding.java is not being cleared, so the nullable instance doesn't get updated.

Reproducible problem:

function test()
	svc iService1?{@BindService {}};
	call svc.test1() returning to ret onException servicelib.serviceexceptionhandler;
end

interface iService1
	function test1();
end


///////////

Add a new function "test2" to iService, and change the call statement to invoke it instead of test1. You'll get an error that there's no such function - because the nullable instance didn't get rebuilt based on the latest binding.
Comment 1 Paul Harmon CLA 2011-09-09 09:19:59 EDT
I have modified the following classes to fix this:

TypeBinding
PartBinding
Binding

I have changed the logic so that the classes clear their own (appropriate)varaiables.
Comment 2 Justin Spadea CLA 2011-09-09 09:31:18 EDT
Fastest fix ever!