For notes on using a workspace of up to V7 in workbench of current version, refer to this section and "B.4.2 Notes on Project Migration".
If a workspace of up to V7 is specified in the Startup dialog box of workbench, then a message box asking whether to update the workspace appears before the workspace is opened. Select [Yes] to update the internal setting information for the workspace, and the workspace will then be ready for use in workbench of current version. If you do not want to update the workspace, select [No] - Workbench will then exit without updating the workspace.
When you first open a workspace of up to V7 with workbench of current version, the perspective is not the one last used in the workspace, but the default one. Open your favorite perspective as necessary. Additionally, if the perspective settings have been customized, then all of them are initialized. Create custom settings as necessary.
The default setting of option 'Build automatically' has been changed to ON. Therefore, incremental build is performed when resources are saved. However, the setting is maintained without change when you open a workspace of up to V7 (which the default setting is OFF), with the workbench of current version. To set automatic build to ON, select [Window] > [Preferences] from the menu bar, select [General] > [Workspace] in the [Preferences] dialog box, then check [Build automatically].
Editor settings, such as fonts, colors, margins, line number visibility, and highlighting, in a version of up to V7 are not maintained by workbench of current version. Make new settings as necessary.
Java Applet launch configuration
The Java Applet launch configuration created in a version up to V7 is not maintained by workbench of current version. Open the workspace, and re-create the Java Applet launch configuration. In the new Java Applet launch configuration, specify the applet display size in [Width] and [Height] on the [Parameters] tab instead of specifying it in an HTML file.
Histories used for JDBC driver names and connection destination URLs
When a database is accessed with a JDBC driver in the Enterprise Bean wizards, the JDBC driver name and connection destination URL are retained in histories, which enables the same values to be re-used the next time the wizards are used. However, the history information retained in a version up to V7 is not maintained by workbench of current version. Enter the JDBC driver name and connection destination URL as new information when using these wizards.
