Updating the J2EE environment file

The J2EE environment file contains a series of entries like the following example:

  <env-entry>
    <env-entry-name>vgj.nls.code</env-entry-name>
    <env-entry-value>ENU</env-entry-value>
    <env-entry-type>java.lang.String</env-entry-type>
  </env-entry>

The order of sub-elements is name, value, type. This is correct for J2EE Web projects; however, for application client and EJB projects, you need to change the order to name, type, value. For the example above, change the order of the sub-elements to:

  <env-entry>
    <env-entry-name>vgj.nls.code</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>ENU</env-entry-value>
  </env-entry>

This step can be avoided if you generate directly into a project instead of into a directory. When you generate into a project, EGL can determine the type of project you are using and generate the environment entries in the appropriate order.

Related tasks
Setting up the J2EE run-time environment for EGL-generated code
Setting deployment-descriptor values

Related reference
Java run-time properties (details)