Community
Participate
Working Groups
I changed the visibility of a method, and the following error message appeared in my task list: Kind Status Priority Description Resource In Folder Location Error The method init(null) from the type com.ibm.etools.ctc.flow.ui.OperationPicker is not visible FlowImplEventPropertyPage.java com.ibm.etools.ctc.flow.ui/src/com/ibm/etools/ctc/flow/ui/properties line 821 in FlowImplEventPropertyPage.tableSelectionChanged() This looks like there was some sort of error in constructing the method signature for the error message.
Note that the sender was actually sending init(null).
Seems we are reconstructing the signature from the argument types instead of the parameter types.
I think the problem is more that the NullBinding readable name is null. When you use null as a parameter, the corresponding binding is the NullBinding. This would explain why null is displayed in the method signature.
null is used as an argument, but the method declared parameter isn't of type NullBinding. This is what my comment was meaning. So I am wondering why we seem to be recreating a signature using the invocation argument types as opposed presenting the declared method signature.
Indeed the problem method binding was created using the parameter types. We should instead use the methodBinding.parameters. I check the fix.
Changes reviewed by Kent. Fixes and released in 2.1 stream. Tests updated.
Verified.