Signals an existing application to shut itself down and reload. This can be useful when the web application context is not reloadable and you have updated classes or property files in the /WEB-INF/classes directory or when you have added or updated jar files in the /WEB-INF/lib directory.
Environment/Instance Properties
Property Name | Required | Description |
|---|---|---|
| Yes | The pathname to the directory in which Tomcat has been installed. |
| Yes | The url of the Manager web application within the Tomcat server. |
| Yes | The name of the Tomcat user with which to connect to the Manager web application. This user must be configured with the manager-script role. |
| Yes | The password for the |
Project Properties
Property Name | Required | Description |
|---|---|---|
| Yes | The context root for the web application being reloaded. The value must start with a forward slash (e.g. /sample). |
Inputs
Input Name | Required | Description |
|---|---|---|
|
|
|
Outputs
Output Name | Required | Description |
|---|---|---|
|
|
|
Artifacts
This operation doesn't consume or produce any artifacts.
...
This plugin has the following pre-requisites:
- The
JAVA_HOMEenvironment variable must be set to a supported JDK for the version of Tomcat being used. - The Tomcat user specified by property
FDTOM_USERNAMEmust be granted the manager-script role. - The target Tomcat server must be running prior to calling this operation.
- An application with the given
FDTOM_CONTEXT_ROOTmust be deployed and be in the running state. - Application reloading (to pick up changes to the classes or web.xml file) is not supported when a web application is deployed directly from a WAR file. It only works when the web application is deployed from an unpacked directory. If you are using a WAR file, you should undeploy and then deploy again to pick up your changes.
...