Tomcat configuration in Eclipse Jee

Source: Internet
Author: User
Tags port number tomcat

Integration of Eclipse Jee with Tomcat, configuration needs to be noted:
- Set Sever Locations
- Configure the server Options
- Configuration Publishing
- Configuration Timeouts
- View Web Modules Server Locations

Specify the path and deployment path for the server
The default option is to use the workspace metadata (does not modify Tomcat installation) to modify the workspace metadata (without modifying the Tomcat installation) to: using Tomcat Installation (takes control of Tomcat installation) using a Tomcat installation (under Tomcat controls)

There is also a typical local configuration (the installation without modifying Tomcat) that is consistent with the default.

when the option turns gray and cannot be changed
Remove the item under Tomcat and modify it after clean. Server Options

Service configuration resolves hot deployment under Eclipse, modifying Java classes and JSP immediate effect issues
Change reloadable= "true" to false so Tomcat does not automatically restart when you save the JSP


Server modules without publishing

By default, the project is deployed to Tomcat, which copies the project to the server path directory shown in server locations. That is, the directory where the workspace resides. Metadata.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps
Selecting this option will publish the project to Tomcat
Web Resource directory: The Webconten of a Web project, the Src/main/webapp directory for a T maven Web project
Class file directory: The output directory of the currently configured class file, the Taget/calsses directory for the MAVEN project
Also modify the servemoduleswithoutpublish=true in Servers.xml and the configuration in Tmp0/conf/server.xml

Publish module contexts to separate XML files

The Servers/tomcat v6.0 Server at Localhost-config/servers.xml will be modified by checking the Saveseparatecontextfiles=true
And the elements of the app in Tmp0/conf/server.xml
Move to Tmp0/conf/catalina/localhost/appname.xml ...
This editor supports Markdown Extra , which expands a lot of useful features. Please refer to [github][2] for details.

Modules Auto Reload by default

Default Auto-load module
Remove this option, this is to modify the class after the self-weight enabled.

Enable Security Enable Tomcat debug Logging (no supported by this TOMCAT version)

These two ignore is good publishing

Modify settings for publishing.
Modify Publishing settings
never publish Automaticall

Do not publish in any case (debug mode, class modification does not restart in effect)

automatically publish when resources change

Automatically released when a resource changes. (The JSP modification will take effect in real time.) Often used in conjunction with Jrebel)

automatically publish after a build event

Published once per specified time

Timeouts

Ports

Start time 45 seconds, stop time 15 seconds. Error after exceeding, debug according to actual situation
Tomcat port number setting Web Modules

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.