This section provides notes specific to the migration of ComponentDesigner resources.
You can use the import functions provided by workbench to migrate ComponentDesigner projects created with Interstage Apworks V5.0 or an earlier version to workbench.
The ComponentDesigner projects that can be migrated are listed below.
Projects that can be migrated |
|---|
Pure Java Application (*1) |
JavaBeans |
Applet |
Enterprise JavaBeans *2) |
Web Application *3) |
Web Application(Apcoordinator) |
*1) Any applications that use the SOAP Server Applications(Apcoordinator) cannot be migrated.
*2) Any Enterprise JavaBeans compliant with EJB 1.0 specification cannot be migrated.
*3) Extension Tag Library applications cannot be migrated.
Note
The following types of projects and applications are not supported by workbench and cannot be imported:
MIDP Application
Enterprise JavaBeans project compliant with EJB 1.0 specification
SOAP Server Application(Apcoordinator)
Extension Tag Library applications
COBOL Application
CORBA Server
CORBA Client
All the classpaths set in ComponentDesigner are added to the build path of the imported project. If any library in classpath is missing, an error occurs during build. Modify the build path appropriately after importing a project.
Batched import of multiple projects
You can import two or more projects in one operation by using ComponentDesigner subprojects. To import them in one operation, follow the procedure below.
Create a work project for this import session in ComponentDesigner; and the project will be used as the parent project of other projects.
In Explorer, open the project folder of one of the projects to be imported. Then, drag the project file project-name.prj and drop it on the project file (work.prj where work is the import work project name) of the import work project displayed in the Project display area in ComponentDesigner.
Click [OK] in the [Add File] dialog box that appears.
The imported project is added as a subproject of the import work project.
Repeat step 2 for each of the ComponentDesigner projects to be imported.
Exit ComponentDesigner.
Start workbench, and select [File] > [Import] from the menu bar.
Select [Existing ComponentDesigner's Project] in [Select an import source].
In the [Project to be Imported], specify the project file of the import work project created in step 1.
Check [Import subprojects], and click [Finish]. The import work project and all its subprojects are imported.
After import is completed, delete the imported import work project from workbench.
For an imported project, the predefined libraries generally used for its project type are added to the build path. To use a predefined library that is not added as a standard library, add the predefined library to the build path.
All the classpaths set in ComponentDesigner are added to the build path of the imported project. If a JAR file that is resolved in a predefined library is directly specified in the build path, it need not be specified in the build path. Remove any such JAR files from the build path to prevent related problems. Another possible problem is that a JAR file cannot be found because its installation folder is different. Remove from the build path those JAR files that are not referenced during Java compilation or that can be resolved in a predefined library. Confirm that each library that you add yourself is at the proper location.
The location of each imported file is determined based on the project type, file type, and file settings at the time of import. In the standard layout of imported files, some files may be placed at locations not appropriate for development with Interstage Studio. After import is completed, confirm that each file is at the proper location; and if it is not, move it to the proper location.
The import function determines file locations based on the following rules:
Java source files (*.java) are placed in the source folder.
The files that are checked as Link to resources on the [Build] tab in the project properties dialog box are placed in the source folder with the original folder structure maintained as is.
The files that are not checked as Link to resources on the [Build] tab in the project properties dialog box are placed in the project folder with the original folder structure maintained as is.
SPT files (*.spt) are placed in the project folder.
If the project to be imported is a Web Application project or Web Application(Apcoordinator) project, its HTML files and JSP files are placed in the ContextRoot folder with the original folder structure maintained as is. However, some JSP files may be placed in the ContextRoot/pages folder.
The HTML files for other project types are placed in the project folder with the original folder structure maintained as is.
If the project to be imported is a Web Application project or Web Application(Apcoordinator) project, the files contained in the WEB-INF folder in the import source project are placed in the ContextRoot/WEB-INF folder.
If the project to be imported is an Enterprise JavaBeans project, the ejb-jar.xml file is placed in the META-INF folder in the source folder.
The application-client.xml file is placed in the META-INF folder in the source folder.
If the ComponentDesigner build option [Treat the Bean serialize files (*.ser) as resources] is checked, all the .ser files at the location immediately under the project folder in the import source project are placed in the source folder.
For a Web Application project or Web Application(Apcoordinator) project, only the HTML files, the JSP files, and the files contained in the WEB-INF folder are placed in the ContextRoot folder. Other files may be placed in the source folder or project folder, depending on whether the file is "Link to resources" or not, with their original folder structures maintained as is.
Confirm the locations of the resource files referenced from within HTML or JSP code, and if necessary, move the files so that their location is appropriate.
Generally, the files defined as "Link to resources" are placed in the source folder. This means that the source folder may be the location of text files and other files that are not to be built. Move files that are not to be built from the source folder to another appropriate location.
