Refer to the following for notes on using a workspace of up to V7 in workbench of current version, and for notes on importing and using a project of up to V7.
The method for referring the JUnit JAR file has been changed. If "ECLIPSE_HOME/plugins/org.junit_3.7.0/junit.jar" has been set as a classpath in a project of up to V7, it should be changed to a new classpath. Delete the traditional junit.jar classpath settings, and instead set the JUnit library in the classpath. The JUnit library is a library installed for referencing JUnit JAR files.
By using "B.6 Automatic Update of the Workspace and Projects", the JUnit classpath can be automatically modified.
Creating an EAR file (earbuild.xml)
If a project of up to V7 uses the EAR file creation function using earbuild.xml, then an EAR file is not created in workbench of current version.
To automatically update the EAR file creation function, follow the procedure described in "B.6 Automatic Update of the Workspace and Projects".
Java compiler build tool settings
If you imported the project of up to V7, then Java compiler build tool settings are not maintained. This is also true if you are using a workspace of up to V7. If the settings have been changed from their default values, then make new settings as necessary.
In the workbench, Web service functions that comply with JAX-WS are standard Web service execution environments. As for applications that use the RPC system of the SOAP service of up to V7, their implementation can be used to the new Java EE Web services, but some of the available types are different. To use the implementation, follow the procedure below (from the viewpoint of interconnection capability, however, it is not recommended to use a WSDL file of up to V7 in current version):
Migrate the implementation.
Migrate the existing implementation while considering changes in data type, differences in the execution environment, and so on.
Expose an implementation class as a Web service.
Add an @WebService annotation to an implementation class to expose it as a Web service.
For details on developing a Web service, refer to "Chapter 5 Developing Web Service Applications".
Using a Web application project
Note the following about using a Web application project:
If a JAR file in the ContextRoot/WEB-INF/lib folder has been added to the project build path, then remove it from the build path. Even if the JAR file is deleted, build can be performed successfully. However, note the following about using the Java editor:
A class defined in the JAR file is highlighted as a problem.
Classes defined in the JAR file are not displayed in candidates of the content assist function.
Using Interstage Application Server V6.0 or earlier servlet containers, servlets could be invoked even if servlet mapping was not defined in web.xml. If using servlets, add the servlet mapping definitions to web.xml. For details, refer to "Interstage Application Server J2EE User's Guide".
The Tomcat launch configuration cannot be used in default setting. If debugging a Web application, debugging using the Servers view is recommended instead.
