- Create async SOA sample project.
- In the project explorer, do Refactor>File Rename to rename AsyncSample.xsd to
- Right click on the renamed file to see that Refactor > Undo|Redo command are
This happen on the second refactorings since the start of the IDE. The main
cause of this "regression" is from the use of
RefactoringManager.isRunning(UsageSet) to filter out noise events. Since this
filtering is less restrictive, the noise events from previous UsageSet listner
could reach RefactoringManager causing reset of undo managers.
The fix is to turn off listening on previous refactored models at the start of
processing the next refactoring.
Also, fix in this change is typo causing memory leaks on listeners attached to
Fix checked into release55_dev:
new revision: 220.127.116.11.2.5; previous revision: 18.104.22.168.2.4
new revision: 22.214.171.124.2.4; previous revision: 126.96.36.199.2.3
new revision: 188.8.131.52.2.1; previous revision: 184.108.40.206
new revision: 220.127.116.11.2.2; previous revision: 18.104.22.168.2.1
new revision: 22.214.171.124.2.2; previous revision: 126.96.36.199.2.1
new revision: 188.8.131.52.2.4; previous revision: 184.108.40.206.2.3
Created attachment 35082 [details]
A much smaller change is needed.
We only need to make sure we detach the RefactoringManager listener from old
usage set together with clear old undo support before processing the next
Created attachment 35097 [details]
A simpler and more effective fix.
Fix committed to release55.
*** Issue 86899 has been marked as a duplicate of this issue. ***
verified in 061011_1