Use Java EE deployment descriptors to define environment references

This rule flags Context <Environment> elements found in the META-INF/context.xml file that must be transformed into <env-entry> elements in the WEB-INF/web.xml file.

Apache Tomcat allows Context <Environment> elements to be defined in these locations:

• The META-INF/context.xml file
• The application XML configuration file in Tomcat conf directory
• The <Host> element in the conf/server.xml

Since the migration tool might not have access to the Tomcat configuration directory, it only flags the Context <Environment> in the META-INF/context.xml file. Context <Environment> information defined in the other locations can be copied to the META-INF/context.xml file in order for it to be processed by the tool.

If a WEB-INF/web.xml exists in the web project:

Context <Environment> elements will be flagged under any of the following conditions:

• The entry does not have a matching entry in the web.xml file.
• The entry has a different type than the matching entry in the web.xml file.
• The entry has a different value than the matching entry in the web.xml and its override flag set to false.

Add a new <env-entry> element in the web.xml file which represents the Context <Environment> element if it does not already exist in the web.xml file. If the entry exists, it will be updated.

If the WEB-INF/web.xml does not exist:

All Context <Environment> elements will be flagged.

Create a WEB-INF/web.xml file that includes the appropriate <env-entry> elements if the web project is at Java EE 5 or higher. The automated fix will report an error if the web project is at J2EE 1.4 or lower.

For example, consider a META-INF/context.xml file with the following content:

with the following web.xml file in the application:

After the automated fix is applied, the web.xml will be updated to contain: