NOTE: This needs to be updated for version 3.0! There are some better ways to do this in 3.0!

VisualAge does an "ok" job when you move classes from package to package. Most references to the class will be updated, but some won't.

Fortunately, VisualAge will quickly flag where the problems are so you can go change them.

A general strategy

When renaming...

Note that VisualAge for Java version 2.0 has a cool bean "morphing" function in the VCE -- you can morph a bean of one type into another and it will retain applicable connections and property settings.