Shulou(Shulou.com)06/02 Report--

This article introduces the relevant knowledge of "the detailed steps of putting the springboot project into a war package to run in tomcat". In the operation of the actual case, many people will encounter this dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

1. You need to set the packaging of the pom.xml file to war.

two。 After changing to a war package, you can directly use the command of maven to type the project into a war package.

3. Put the war package directly into tomcat and run it.

4. When you start startup.bat, you can find that the console does not print the springboot startup message.

From the tomcat startup information above, you can see that springboot is not started, that is, the environment of spring and the environment of springmvc are not initialized. So there is no access to the project.

Based on this result, we were thinking, why can't we start the springboot environment? That is, when we started our war package with tomcat, tomcat did not execute to our main class (startup class).

So how do we get tomcat to execute to our main class when it starts?

5. In springboot's startup class, inherit the SpringBootServletInitializer class and override the configure () method; then use maven's package command to rewrite the war package, which allows tomcat to execute to our main class when it starts.

At this time, we put the typed war into the tomcat to run, and we can see that the springboot startup message has been printed, that is, the environment of spring and springmvc has been initialized.

6. Why can the main class in springboot be executed to our main class after inheriting SpringBootServletInitializer,tomcat?

This question is about to involve the new features of servlet3.0:

As you can see from the figure above, servlet3.0 provides us with a very powerful specification, and as long as we follow this specification, we can remove web.xml when tomcat starts and initialize the spring environment.

1. A new specification is defined: under the META-INF/services folder of the resource file, there is a file named javax.servlet.ServletContainerInitializer that defines the full class name of your own class. At the same time, this class implements the javax.servlet.ServletContainerInitializer interface and overrides the onStartup method

two。 Under the above specification, all servlet servers that follow this specification, such as tomcat, reflect the onStartup () method that executes this class on their own when the service starts.

3. Through this new specification, we do not need to follow the traditional method, we need to initialize the configuration and environment such as spring in the web.xml file, so we can achieve zero configuration. Springboot achieves zero configuration according to this idea.

This is why when a springboot project starts with tomcat, it needs to implement the SpringBootServletInitializer class and override the configure method.

This is the end of the content of "detailed steps for running the springboot project into a war package in tomcat". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.