Refer to the following cautions when using a V10 workspace in this version's workbench.
The Template view that was provided with the V10 Compatible Workbench is not provided in the Java EE workbench. If a V10 Compatible Workbench workspace is opened in the workbench of this version, the template of the Template view that was used in the V10 Compatible Workbench can be used in the workbench. Templates for files with the extension java, xml, html, htm, jsp, js, css, dtd, and sql can be used. These templates can be used as the templates of each corresponding editor.
To use a template that was used in a V10 workbench Template view as the template of each editor, the template must be migrated. The procedure for migrating templates is shown below:
From the menu bar, select [Project] > [Update Workspace/Projects of Previous Version].
The [Update Workspace/Projects of Previous Version] dialog box is displayed. If update of the workspace has not been implemented, "Workspace" will display on the left side of the dialog box. Select "Workspace", and then click [OK]. The files required for template migration are generated.
Copy the following files to any projects for work use.
<workspace folder>\.metadata\templateBackups\studioTemplates.xml
Open the copied XML files in an XML editor. The opened XML file will be in the following tree structure:
<syntaxtemplate>
+ <root>
+ <category>
+ <template>The name attribute of the <template> element is the name of the template. The description attribute is the description of the template. The context attribute is the context. The child text of the <template> element is the template.
Delete templates that do not require migration. To delete, in the XML editor design page, delete the <template> element.
The context of non-Java templates is not set. The attribute value of the context attribute is a null string. Enter an appropriate context in the context attribute. If the file type is not modified, the context can be modified after the import. Therefore, set the following values for each file type you want to import.
File Type | Attribute Value of Context Attribute |
|---|---|
Java | Java |
XML | xml_all |
CSS | css_all |
DTD | dtd_new |
HTML | html_all |
JavaScript | javaScript |
JSP | jsp_all |
SQL | org.eclipse.datatools.sqltools.editor.template.sql.generic |
Open the source page of the XML editor, and modify the variable name. In the V10 Compatible Workbench, the variable name was not limited to the ${xxx} format, and Japanese characters etc could be used. In the workbench of this version, only alphanumeric characters and underscores ("_") can be used in the variable name. Migration cannot be performed if other characters are used.
Import templates from the template settings of each corresponding editor. With import, only the context templates associated with that editor are imported.
Migrating J2EE Associated Templates
A template definition file is prepared for the following J2EE templates.
Context | Name | Description |
|---|---|---|
Java | EJB Home reference | Performs reference processing for EJB Home. |
EJB Local Home reference | Performs reference processing for EJB Local Home. | |
MessageProducer | Sends a message to the EventChannel. | |
Point-To-Point | Sends a message to the queue. | |
Publish/Subscribe | Sends a message to the topic. |
Import and apply the definition file as required. The procedure for applying the definition file is shown below.
From the menu bar, select [Window] > [Preferences].
The [Preferences] dialog box is displayed. Select [Java] > [Editor] > [Templates].
The [Templates] page is displayed. Click [Import].
The [Importing Templates] dialog box is displayed. Specify the following file to import the template definition.
<Workbench installation folder>\etc\templates\templates_ejb_jms.xmlIf a V10 Compatible Workbench workspace is opened in the workbench for this version, there are some tags and attributes defined in the Snippets view that cannot be used in the workbench. To prevent these tags and attributes from displaying in the Snippets view, the following definition file must be deleted:
<user document folder>\Interstage Studio\workspace\.metadata\.plugins\org.eclipse.wst.common.snippets\user.xml
Note
If individual tags were registered in the Snippets view of the V10 workbench, and the above-mentioned definition file is deleted, the individual tag information is also deleted. Therefore, use the customization function of the Snippets view again to register the tags.