| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> |
| <html> |
| <head> |
| <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." > |
| <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> |
| <meta http-equiv="Content-Style-Type" content="text/css"> |
| <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]"> |
| <title> |
| Refactoring |
| </title> |
| <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css"> |
| </head> |
| <body> |
| <h1> |
| Refactoring |
| </h1> |
| <p> |
| The goal of refactoring support is to allow for improving your code without changing its behavior. When you refactor your code, your goal is to make a system-wide coding |
| change without affecting the semantic behavior of the system. The JDT automatically manages refactorings for you. |
| </p> |
| <p> |
| Refactorings which change method signatures allow to keep the original method to preserve not only the semantic of your code, but also the |
| interfaces. This allows you to change methods in API types without breaking your clients. |
| </p> |
| <p> |
| The workbench optionally allows you to preview all the impending results of a refactoring action before you finally choose to carry it out. |
| </p> |
| <p> |
| Refactoring commands are available from the context menus in many views and editors and the <a href="ref-menu-refactor.htm">Refactor menu</a> in the menu bar. |
| </p> |
| <p> |
| <img src="../images/ngrelc.png" alt="Related concepts" border="0" > |
| </p> |
| <p> |
| <a href="../concepts/concepts-9.htm">Refactoring support</a> |
| </p> |
| <p> |
| <img src="../images/ngrelr.png" alt="Related reference" border="0" > |
| </p> |
| <p> |
| <a href="ref-menu-refactor.htm">Refactoring actions</a><br> |
| <a href="ref-117.htm">Refactoring wizard</a><br> |
| </p> |
| |
| </body> |
| </html> |
| |
