user level handle on refactoring...

Is there a way for me to get a handle on what refactoring I did? This is what I am looking for:

I have a class that becomes a managed resource through model mbeans. In my mbeans-descriptor file I have defined various methods and their parameters. Of-course the name of the actual class itself does not appear in the xml file.

When I do a refactoring (especially change method signature, rename a method), I would like to be able to figure out that the method is being used in the xml file and get a post-refactoring handle that will allow me to modify the xml file if required. Or at least pop that up as a usage so that I know I need to fix it. Again realize that there is no direct connection between the class being managed and the xml file. Here is an example:

    
      
      
      
     
 ]]>


and the java code snippet is:

3 comments

You can enable "search in non-java files" in the refactoring, I think.

0

Rename method at least has a way of searching strings and comments but not the non-java file (I am using 1171). Change method signature does not have even that. I tried doing these 2 refactorings to see if I could get IDEA to realize that mbeans-descriptor file also needs to be changed.

0

Vinay Moharil wrote:

>Rename method at least has a way of searching strings and comments but not the non-java file (I am using 1171). Change method signature does not have even that. I tried doing these 2 refactorings to see if I could get IDEA to realize that mbeans-descriptor file also needs to be changed.
>
>

>
If you now have the time you could start a plugin for that (I don't).
There is an old request
http://www.intellij.net/tracker/idea/viewSCR?publicId=12113 asking for
the move/rename refactoring to be extendable for frameworks to register
their own custom rename/move handler to handle any side effects on other
files... The JUnit plugin started on by exploiting the refactoring
listeners. However there is no extension points to merge all side
effects into one refactoring so it has to go through 2 rename/moves (one
for the class and one for the test class). Ideally it would be like
renaming a field where both setter and getter are listed together with
the field in the preview and refactored together.

Jacques

0

Please sign in to leave a comment.