Tokava is a well known optimization tool that can be used for the task of refactoring a Java application. This Java Enterprise Application will allow for faster application startup and overall performance. However, before you can refactor your application you should know what is involved with this process. In this article I will describe the basics of how to approach the refactoring task.

To begin, the developers at Tokava have designed a refactoring tool that uses the foundation of Agile model that works well in the case of Java applications. The feature that will enable you to refactor Java application is called "evolve" that makes it possible to evolve the application without making drastic changes in any of the underlying classes or objects. Once the developer has evolved the application it will become more mature and can then be brought to the next level. The next thing that we will talk about is what is to be done when you are going to evolve the code.

When you start refactoring an application you should understand that there are two kinds of refactoring, the traditional and the non traditional refactoring. With traditional refactoring the programmer makes use of all the features provided by the Swing architecture. However, when using the traditional method the programmer has to go through the hierarchy of classes just to find the object that needs to be modified. This is because the Swing architectural design does not provide support for the traditional code transformations. The non traditional method on the other hand only makes use of the inheritance and static typing provided by the Agile design.

When we are going to look at the process of applying the Tok99 refactoring converts we will come across a few different techniques. The first one is known as instance method. With the tok95 the developer has to write an instance method once for each object he is about to modify. In the Agile approach every object has its own instance and hence there is no need to write instance methods for every object. Another difference is that in the Agile method the instance method for a class is directly called which saves a lot of time and thus makes the overall process very smooth.

The second kind of refactoring is known as superclass pattern. With the tok99 the developer has to create a superclass pattern which contains all the methods of the derived subclasses of every object. The benefit with the superclass pattern is that it makes the overall modification process very easy.

The last one is known as template method. With the tok99 the programmer has to create a template method for each type of object and associate the corresponding generic function as the delegate. The benefit with the template method is that the generic functions can be varied independently and hence the overall programming process becomes more flexible. All the three patterns discussed above are very useful in Agile refactoring.