How to programmatically rename a method using JDT

Question

My aim is to programmatically call the Refactor >> Rename Eclipse command for a method inside a Java Source File. Renaming a method as such should also apply the change to all the instances where this method is being used/referred.

I believe that JDT has a Refactoring API, but not able to find any documents or tutorials for the same.

Can somebody point me in the right direction.

Edit: The change is not needed at runtime.

Lucey

#1712771 might hint you in the right direction - it shows at least some method handling jdt functionality – Khalid

I don't know if it's possible. You can do that by using ANT script before compilation. Your classes are not dynamic and you doesn't use dynamic class loading. – Greenberg

@Fess: I think u misunderstood my question. Its not for class files but for Java source files. I have updated the question to reflect this. – Lucey

Try use JCodeModel link or Eclipse JDT's AST: link – Greenberg

Did I understood you correctly that you want to do this at runtime? – Heartrending

Answer 1

I think your most promising approach is to go to the eclipse source code.

1. Download the release you want, with source code. In particular, you want the source for the JDT plugins, which is included in the 'classic' release. All of the following is based on 4.2.1.
2. Boot up in to an empty workspace.
3. File->Import: Plug-ins and Fragments
4. Import from "The active target platform", "Select from all...", "Projects with source folders"
5. Select at least org.eclipse.jdt.ui and org.eclipse.ltk.core.refactoring.

The starting point corresponding to Refactor >> Rename is org.eclipse.jdt.ui.actions.RenameAction. That's for the overall rename refactoring though, it can rename anything from methods to files. More relevant for you is RenameSupport.create(IMethod, String, int).

You can see there that a RenameRefactoring class is created around either a processor, either a RenameVirtualMethodProcessor or a RenameNonVirtualMethodProcessor, and then sent to a new instance of RenameSupport. RenameSupport handles all the UI to configure your refactoring, but since you're doing it programatically you just need the RenameRefactoring and the processor, configured using the various processor.set*() methods.

Now you have a configured instance of RenameRefactoring. Now what? The actual operation in Eclipse is executed across two Job implementations. Take a look at RefactoringExecutionHelper.Operation and PerformChangeOperation for the details.

What does this all boil down to? Leaving aside all the fine details of exception handling, having an undo stack, and workspace checkpoints, you could rename a 'virtual' method using these steps:

IMethod methodToRename = <....>
RenameMethodProcessor processor = new RenameVirtualMethodProcessor(methodToRename)
processor.setUpdateReferences(true);
processor.setNewElementName("newMethodName");

RenameRefactoring fRefactoring = new RenameRefactoring(processor);
fChange= fRefactoring.createChange(new NullProgressMonitor());
fChange.initializeValidationData(new NullProgressMonitor());
fChange.perform(new NullProgressMonitor())

There's a lot of support code in there for undo, progress bars, async execution, workspace checkpoints etc, which you may or may need depending on how you want to run this. But that's the guts of how to run the refactoring.

Oppugn

Thanks! that was exactly a type of answer what i needed, +1, let me check if can get the code to work. Do you know any websites resources or explanations online for this ?? – Lucey

Not really. A few about how to write new refactorings to plug in to the IDE (eg #1314708) but not anything about calling the existing refactorings in different ways. – Oppugn

hi thanks for the link. waiting answers from other persons too. – Lucey