Setting the EGL migration tool preferences

Before you can use the EGL migration tool, you must set its preferences.
To set the EGL migration preferences:
  1. Click Window > Preferences.
  2. Expand EGL and click Migration. This page shows the settings for the migration tool.
  3. Choose how to resolve naming conflicts by using reserved words:
    • Select Add suffix to set the migration tool to add a suffix to all words in the source code that are reserved words. In the text box near this radio button, type the suffix you want the migration tool to add to the changed word.
    • Select Add prefix to set the migration tool to add a prefix to all words in the source code that are reserved words. In the text box near this radio button, type the prefix you want the migration tool to add to the changed word.
  4. If your project has standalone functions (functions that are not contained by other logic parts), and those functions contain variables that are now reference types (such as arrays), select Convert assignment statements to move statements. For more information about converting from assignment to move statements for reference variable, see “Changes made by the V7.0 migration tool.”
  5. The I4GLItemsNullable property replaced the itemsNullable build descriptor option; for more information, see the section about nullable types in “Changes made by the V7.0 migration tool.” The migration tool can add the I4GLItemsNullable property to your logic parts automatically. To add the property, select Add property I4GLItemsNullable=yes.
  6. To preserve the way that EGL treats text literals (such as "Hello!"), for each part, set the textLiteralDefaultIsString property to NO. For more information, see “textLiteralDefaultIsString.”
  7. To set the migration tool to delete the Java™ files from your projects so that the Java files can regenerate from the EGL source, select either Prompt, Always, or Never. This change affects the Java files in the same project as the EGL code that you are migrating. If you are generating the EGL code into a different project, manually delete those Java files.
  8. The migration tool can set the deploymentDescriptor build descriptor option to the name of an EGL deployment descriptor file in the project. It can update all build descriptor files, the default build descriptors only, or none at all. To set this preference, select a radio button under "Project build descriptors to update with the deployment descriptor name".
  9. The migration tool can add web service deployment information to the deployment descriptor file of a project for each Service part it finds in the related project. To set this preference, select an option under "Add a webservice element to the deployment descriptor for every service".
  10. The migration tool can remove web service references from the J2EE deployment descriptor because EGL uses its own deployment descriptor file for service references. If you want the migration tool to make this change, select Remove web service references from the J2EE deployment descriptor.
  11. EGL V6.0 migration only: To add level numbers to Record parts that do not have level numbers, in the Default level number for record structure field, set the default level number.
  12. EGL V6.0 migration only: To add a qualifier to the values of properties that have a finite list of possible values, select Add qualifiers to enumeration property values. If you select this check box, the migration tool adds the type of value to the value name.
  13. Under "Logging options", make two choices:
    • Whether you want the tool to add a comment to each file that it changes
    • Whether you want the results of the migration process to be saved in a log file
  14. When you are finished setting preferences, click OK to save your changes.

Feedback