<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>
<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 runtime environment for EGL-generated code
Setting deployment-descriptor values
Related reference
Java runtime properties (details)