When deploying a project, if I haven’t configured a web.xml for my own project, all request links will use the configuration information from Tomcat’s web.xml, such as the homepage, session timeout, etc.
The web.xml in Tomcat is a global configuration. If you don’t set one, it defaults to Tomcat’s web.xml. If you do set one, the settings in your project’s web.xml naturally take higher priority:
Here is an example of the session timeout setting. The timeout configuration under the project will be used first, and the global tomcat/conf/web.xml file will be ignored:
銆€銆€The loading order is
1. The Tomcat software’s conf directory;
2. The project’s own directory;
銆€銆€The Tomcat config directory serves as the global server scope, typically used for global settings, data sources, etc., while the project