Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 370655 - [refactoring] change method signature of a callin bound method fails
Summary: [refactoring] change method signature of a callin bound method fails
Status: VERIFIED FIXED
Alias: None
Product: Objectteams
Classification: Tools
Component: OTDT (show other bugs)
Version: 2.0.1   Edit
Hardware: Other Linux
: P3 normal (vote)
Target Milestone: 2.0.2   Edit
Assignee: Stephan Herrmann CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-05 08:24 EST by Stephan Herrmann CLA
Modified: 2013-01-15 16:42 EST (History)
0 users

See Also:

Attachments
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 Stephan Herrmann CLA 2012-02-05 08:24:06 EST 
In the reachability example I tried to refactor the bound role method Inheritance#checkAgainstInheritedMethods(..) as to remove the last (unused) parameter "length".

The refactoring signals:
"Cannot update found node: nodeType=85 ..."
I.e., this refactoring has a switch of node types that doesn't handle MethodSpec.
Comment 1 Stephan Herrmann CLA 2012-02-05 14:46:10 EST 
This is mostly a dup of bug 311879.

Still seeing this in 2.0.2 candidates is strange.
One theory is that a missing mentioning in plugin.xml of a nested team is the culprit.
This is fixed in commit b19dd7a7a149bc830a01cdb5a7bb4a575cb798ac
After patching otdt.refactoring with an updated plugin.xml the bug disappeared.
Comment 2 Stephan Herrmann CLA 2012-02-05 15:05:50 EST 
Released also for 2.1 M6 via 08ed11af6b4c66a0888b3147547fd73418940f00
Comment 3 Stephan Herrmann CLA 2012-09-18 18:01:21 EDT 
If the callin has no signatures, this still doesn't work. I filed bug 390950 for this.

The original problem has been verified using OTDT 2.2.1.201209181302.
Comment 4 Stephan Herrmann CLA 2012-09-18 18:02:22 EDT 
(In reply to comment #3)
> If the callin has no signatures, this still doesn't work. I filed bug 390950
> for this.

oops, should've read: bug 389850.