Bugzilla – Full Text Bug Listing
| Summary: | Nullable type not cleared in TypeBinding on reset | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Justin Spadea <jspadea> |
| Component: | EDT | Assignee: | Paul Harmon <pharmon> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
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. Fastest fix ever! |
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.