Last May, during my employee evaluation, my boss set getting certified in Visual Age Java as one of my goals to be completed by August. I spent several months avoiding that goal because the tool seemed clumsy and artificial to me. I much preferred writing my Java code by hand using a text-editor like Multi-Edit.

I am a hard-core hand coder. I like the control I have over my code in an editor and shy away from code generators like the Black Death. Thus, what I am about to say is shocking, even to me.

I like Visual Age Java.

In fact, I am having a lot of fun working with it, and am actually looking forward to earning this certification. The change has only recently come about. Last month, I started working with Visual Age because I needed to rapidly develop a graphical user interface for my current project.

I started working through some of the VA tutorials in order to bring myself up to speed on the tool, and in no time at all I was hooked. I won’t lie to you. Using VA is nowhere near as easy as coding with Visual Basic. However, VA is a powerful application that gives the developer the ability to quickly piece together Java applications.

My company owns the Professional edition of version 3.5 of Visual Age Java. It came as part of a set of Websphere development tools. In addition, I now own my own copy of 3.5 Professional. It came as part of a tutorial package that I purchased from IBM. Typically, Visual Age Java sells for approximately $150. However, it comes packaged with The Ultimate IBM Visual Age for Java Tutorial, published by IBM press. I paid $69 for the tutorial set from BarnesAndNoble.com.

Features

One feature that jumps right out for new developers is the code repository. Typically, java classes are stored in plain text files and are managed like any other text file. However, in VA, code is stored in a database called the repository. Through the repository, you have the ability to maintain different versions of your code and manage code changes.

When I first started using VA, I hated the repository. I missed my familiar and comfortable text files. Eventually, however, the repository grew on me. I am not as excited about it as IBM, but it no longer makes me snarl.

The next feature of concern is the code editor. Once again, this took some getting used to. I was accustomed to opening a text file containing a single Java class, and being able to see everything at a glance. The VA editor works a bit differently. Instead of bring up an entire class in the editor, VA only shows you the method that you are currently working on. In addition, whenever you save your work, the editor automatically compiles your code and alerts you to errors.

In version 3.5, IBM finally added the ability to view your source directly. I assume that enough programmers screamed and whined that IBM finally relented and added the feature. Honestly though, I don’t find myself using it that often anymore.

Up until now, I have merely described a product that has an editing and code storage system that can make experienced coders cranky. Why would anybody rave about this product?

The real joy in Visual Age Java comes when you are developing, yes- you guessed it, visually. In the Visual Composition Editor, you have the ability to visually work with Java beans and create complex programs with a few clicks of your mouse. Visual Age allows you to make connections to the various beans using context menus and represents those connections with colored lines. In addition to making development easy, this method also assists with documentation. The connections and beans that are visible on the editor are a great start for documenting how the various Java objects interact, and where everything fits in the system.

The final feature that I should note is the integrated debugger. It works as most debuggers do. It allows you to set breakpoints, step through your code, and peek at the value of your data objects. I haven’t found anything exceptional about the debugger, but it does work as advertised.

Shortcomings
As much as I have grown to love Visual Age, I do still have some complaints. The program help is less than helpful for one. IBM seems to rely on their website to provide program help, and anyone who has used IBM’s site at all knows that it is less than organized. However, if you dig around a bit, there are some excellent tutorials and resources out there. The trick is finding them.

My other complaint is that the software does tend to crash. If you use it right out of the box, be prepared for at least one or two crashes a day. The trick is to go immediately to the IBM web site and download Fix Pack 2 and install it. This seems to have stabilized my copies both at home and at work.

Ease of Use
You need to know Java pretty well before you can hope to be really proficient with Visual Age Java. A basic understanding of Beans and Swing is essential. In addition, you will need to practice a bit and get used to developing the VA way.

Like any other new development tool, you will probably find that Visual Age slows you down a bit when you first start using it. However, once you get a feel for the interface, I believe you will discover that you can use it to rapidly develop Java applications with ease. It is a powerful tool that has the potential to save you hours of effort when coding your applications.

Conclusions
Of all the Integrated Developer Environments that I have tried for Java, Visual Age is the only one I would recommend. It does take some getting used to, but once you get a feel for it, I am sure you will find that it will save you time and effort.

If you are buying the Professional edition for yourself, check out the IBM Ultimate Visual Age for Java tutorial. The tutorials are a great aid for getting started, and you will save more than 50% of the purchase price for the software.

Recommended: Yes