![]() Version: 9.4.27.v20200227 |
private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services for sponsored feature development
Jetty server instances that configure the deploy module will have a web application deployer that hot deploys files found in the webapps directory.
Standard WAR files and Jetty configuration files that are placed in the webapps directory are hot deployed to the server with the following conventions:
example/ is deployed as a standard web application if it contains a WEB-INF/ subdirectory, otherwise it is deployed as context of static content.
The context path is /example (that is, http://localhost:8080/example/) unless the base name is ROOT (case insensitive), in which case the context path is /.
If the directory name ends with ".d" it is ignored (but may be used by explicit configuration).example.war is deployed as a standard web application with the context path /example (that is,
http://localhost:8080/example/).
If the base name is ROOT (case insensitive), the context path is /.
If example.war and example/ exist, only the WAR is deployed (which may use the directory as an unpack location).example.xml is deployed as a context whose configuration is defined by the XML.
The configuration itself must set the context path.
If example.xml and example.war exists, only the XML is deployed (which may use the WAR in its configuration).If you have a standard web application, you can hot deploy it into Jetty by copying it into the webapps directory.
The demo-base/webapps directory contains the following deployable and auxiliary files:
ROOT/test.dtest.xml to inject extra configuration into test.war.test.xmltest.war.
The additional configuration includes the context path as well as setting additional descriptors found in the test.d directory.test.wartest.xml.async-rest.wartest-jaas.wartest-jaas.xmltest-jaas.war.
Additional configuration includes setting up the LoginService for authentication and authorization.test-jndi.wartest-jndi.xmltest-jndi.war.
Additional configuration includes defining objects in the naming space that can be referenced from the webapp.test-spec.warServletContainerInitializers and other Servlet Specification 3.0/3.1 features.test-spec.xmltest-spec.war.
Additional configuration includes setting up some objects in the naming space that can be referenced by annotations.javadoc-proxy.warexample-moved.xmlMovedContextHandler to redirect from one path to another.