#Tomcat 7 download update#

Delete the and elements then delete the !- string at the beginning and the - string at the end of the element. The standard releases of XNAT 1.8.2 and later already have the lines required for Tomcat 7 compatibility, but they're commented out.

The final version of your modified configuration file should look like this:

Continue with your deployment/installation using the updated war file in place of the standard XNAT application.

#Tomcat 7 download update#

Update the war file with your modified META-INF/context.xml file: $ jar uf xnat-web-1.8.2.war META-INF/context.xml

Edit META-INF/context.xml and delete the lines with the, and elements.Īdd the following lines to the file right after the element:.

This file should look something like this (edited for clarity): If you have Tomcat 7.0, you should consider upgrading to Tomcat 8.5 or later, but if you can't, follow these instructions to restore compatibility with Tomcat 7.0:Įxtract the file META-INF/context.xml (this requires having the Java JDK available on your path): $ jar xf xnat-web-1.8.2.war META-INF/context.xml The default war for XNAT 1.8.2 and later is built to run under Tomcat 8.5 and later. Running XNAT 1.8.2 and later on Tomcat 7.0 XNAT 1.8.1 and earlier requires no changes to run on Tomcat 7.0. Running XNAT 1.8.1 and earlier on Tomcat 7.0 If you are using Apache Tomcat 7, we recommend using Tomcat 7.0.106 or later or upgrading to Tomcat 9.0 (if you are running XNAT 1.8.1 or earlier, we recommend upgrading to XNAT 1.8.2 or later to run with Tomcat 9.0, but if this isn't possible you can modify your older XNAT to run on Tomcat 8.5 or later). This has been generally reported on StackOverflow, and reported as an XNAT bug here. With the move to Java 8, XNAT 1.8 snapshot builds began seeing severe Catalina errors on versions of Tomcat prior to version 7.0.106.