The difference between core and deployer on the Tomcat website

 

 

 

Please see the README file for packaging information. It explains what every distribution(分布) contains.

 

Binary Distributions

 

• Core:

  • zip (pgp, md5, sha1)

  • tar.gz (pgp, md5, sha1)

  • 32-bit Windows zip (pgp, md5, sha1)

  • 64-bit Windows zip (pgp, md5, sha1)

  • 32-bit/64-bit Windows Service Installer (pgp, md5, sha1)

• Full documentation :

  • tar.gz (pgp, md5, sha1)

• Deployer:

  • zip (pgp, md5, sha1)

  • tar.gz (pgp, md5, sha1)

• Extras:

  • JMX Remote jar (pgp, md5, sha1)

  • Web services jar (pgp, md5, sha1)

• Embedded:

  • tar.gz (pgp, md5, sha1)

  • zip (pgp, md5, sha1)

    Source Code Distributions

 

• tar.gz (pgp, md5, sha1)

• zip (pgp, md5, sha1)

  Seeing here, everyone knows that the same version of Tomcat has different download versions. You should be able to distinguish Binary Distributions and Source Code Distributions , which are the binary version and the source code book respectively. The confusion is that there are two Core and Deployer under Binary Distributions . What is the difference between these two? Which should we choose?

   

  Let's talk about the difference first.

   

  Core : It is the official binary release version of Tomcat . Generally, everyone should download Core when doing development or learning .

  Deployer : It is a publisher of web applications based on Tomcat , that is, when publishing a written JavaEE application to Tomcat , Deployer can be used to dynamically publish. So it's not a real Tomcat binary version, it's just a publishing tool for publishing Tomcat -based web applications. Therefore, you should not download this thing when downloading, unless you want to dynamically publish Web applications to Tomcat .

   

  So since Deployer is used to publish Web applications to Tomcat , what can it do?

   

  It is necessary to explain to you the concept of Web application publishing in Tomcat .

  Publishing: Refers to the process of installing a Web application into the Tomcat server.

  There are two ways to publish a web application in Tomcat :

  1. Static publishing: refers to copying the completed Web application directly to the Tomcat server when Tomcat is not started .

  2. Dynamic release: there are two situations

          2.1   refers to the dynamic operation of published web applications through Tomcat 's automatic deployment function when Tomcat is already running .

          2.2   refers to publishing the finished web application to the running Tomcat through the Tomcat Manager web application remotely .

   

  The role of Deployer is reflected in the dynamic release of Web applications to Tomcat .

  Deployer is a command-line tool that can compile and verify Web applications, and can package all resources of Web applications into War files .