A server failure may
cause cause IDE errors on the client, or prevent you from saving the workspace. After the
server has been restarted, you may be able to reconnect without losing any work. See the
list of related topics at the end of this document, for a link to more information on
recovering from a server failure.
Workspace Recovery
If VisualAge for Java terminates abnormally, for example because of a power
failure, the workspace is not saved. If something causes the workspace to become
corrupted, you can not save it. In either of these situations, you will not lose the
source code changes that you have saved; they are safely stored in the repository and
can be re-added to the workspace if necessary. You may lose some workspace
information, if you have made any of the following changes since the last time you saved
the workspace:
To recover from a corrupted workspace error or from an IDE failure:
Failure to Recover a Corrupted Workspace
When you try to restart the IDE, you may see a message indicating that VisualAge
for Java could not recover the workspace. If this happens, you must restore the workspace
file, ide.icx.
If you have a backup copy of the ide.icx file, restore that. If you do not have a backup copy, you will have to reinstall the workspace that was provided with VisualAge for Java, as described below.
Once you have restored the workspace file and restarted the IDE, you can retrieve the work you had saved in the repository by re-adding or replacing your open editions in the workspace, and you can reset your IDE options. When you have recustomized the workspace, select Save Workspace from the File pull-down menu.
Reinstalling the Workspace
To reinstall the original VisualAge for Java workspace file:
Your workspace should now be fully recovered and ready to use.
Saving the Workspace
Adding Projects and Packages from the Repository to the
Workspace
Adding Classes and Methods from the Repository to the
Workspace
Replacing Editions in the Workspace (Reloading)
Setting IDE Options