Merge remote-tracking branch 'origin/jetty-10.0.x' into jetty-10.0.x-5264-demo-modules
This commit is contained in:
Joakim Erdfelt
commit
09d159d038
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Enables Annotation scanning for deployed webapplications.
|
||||
Enables Annotation scanning for deployed web applications.
|
||||
|
||||
[depend]
|
||||
plus
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Integration of CDI within webapp to Jetty container object lifecycles.
|
||||
Provides integration of CDI within webapp to Jetty container object lifecycles.
|
||||
This module does not provide CDI, but configures jetty to support various
|
||||
integration modes with a CDI implementation on the webapp classpath.
|
||||
CDI integration modes can be selected per webapp with the "org.eclipse.jetty.cdi"
|
||||
|
|
|
|||
|
|
@ -2,8 +2,9 @@
|
|||
|
||||
[description]
|
||||
Jetty setup to support Decoration of Listeners, Filters and Servlets within a deployed webapp.
|
||||
This module uses the DecoratingListener to register an object set as a context attribute
|
||||
as a dynamic decorator. This module sets the "org.eclipse.jetty.webapp.DecoratingListener"
|
||||
This module uses DecoratingListener to register an object set as a context attribute
|
||||
as a dynamic decorator.
|
||||
This module sets the "org.eclipse.jetty.webapp.DecoratingListener"
|
||||
context attribute with the name of the context attribute that will be listened to.
|
||||
By default the attribute is "org.eclipse.jetty.webapp.decorator".
|
||||
|
||||
|
|
|
|||
|
|
@ -52,30 +52,46 @@ For more detailed information about the Jetty module system, see xref:og-modules
|
|||
[[og-begin-arch-jetty-base]]
|
||||
===== Eclipse Jetty Architecture: `$JETTY_BASE`
|
||||
|
||||
After installing Jetty in `$JETTY_HOME`, you want to create another directory that will be referred to as `$JETTY_BASE`, likely in a different location in the file system from `$JETTY_HOME`.
|
||||
Instead of managing multiple Jetty implementations out of several different distribution locations, it is possible to maintain a separation between the binary installation of the standalone Jetty (known as `${jetty.home}`), and the customizations for your specific environment(s) (known as `${jetty.base}`).
|
||||
In addition to easy management of multiple server instances, is allows for quick, drop-in upgrades of Jetty.
|
||||
There should always only be *one* Jetty Home (per version of Jetty), but there can be multiple Jetty Base directories that reference it.
|
||||
|
||||
The `$JETTY_BASE` directory is where you configure which Jetty modules you want to use and what configuration they have, and it is the base directory where you deploy your web applications.
|
||||
You do not deploy your web applications in `$JETTY_HOME`, you deploy them in `$JETTY_BASE`.
|
||||
|
||||
You can have just one `$JETTY_HOME` but multiple `$JETTY_HOME` directories, each with its own configuration.
|
||||
|
||||
This separation between `$JETTY_HOME` and `$JETTY_BASE` allows to upgrade Jetty without affecting your web applications.
|
||||
This separation between `$JETTY_HOME` and `$JETTY_BASE` allows upgrades without affecting your web applications.
|
||||
`$JETTY_HOME` contains the Jetty runtime and libraries and the default configuration, while a `$JETTY_BASE` contains your web applications and any override of the default configuration.
|
||||
|
||||
For example, with the `$JETTY_HOME` installation the default value for the network port for clear-text HTTP is `8080`.
|
||||
However, you want that port to be `6060`, for example because you are behind a load balancer that is configured to forward to the backend on port `6060`.
|
||||
|
||||
If you had changed the default configuration in `$JETTY_HOME`, when you upgrade Jetty, say from version `10.0.0` to version `10.0.1`, your change will be lost.
|
||||
You would have to remember all the changes you made to the default configuration, upgrade Jetty (which would overwrite the configuration files with the default values), and made again all the changes, which results in a maintenance nightmare.
|
||||
|
||||
Instead, you want to configure the clear-text HTTP port in your `$JETTY_BASE`.
|
||||
When you upgrade Jetty, you will upgrade only files in `$JETTY_HOME`, and all the configuration in `$JETTY_BASE` will remain unchanged.
|
||||
|
||||
Installing the Jetty runtime and libraries in `$JETTY_HOME` also allows you to leverage file system permissions: `$JETTY_HOME` may be owned by an administrator user (so that only administrators can upgrade it), while `$JETTY_BASE` directories may be owned by a less privileged user.
|
||||
|
||||
[IMPORTANT]
|
||||
====
|
||||
Install Jetty and never modify the files under `$JETTY_HOME`, unless you are upgrading Jetty itself.
|
||||
If you had changed the default configuration in `$JETTY_HOME`, when you upgrade Jetty, say from version `10.0.0` to version `10.0.1`, your change would be lost.
|
||||
Maintaining all the changes in `$JETTY_HOME`, and having to reconfigure these with each upgrade results in a massive commitment of time and effort.
|
||||
|
||||
Do all the rest in `$JETTY_BASE`.
|
||||
====
|
||||
To recap:
|
||||
|
||||
`$JETTY_BASE`::
|
||||
* This is the location for your configurations and customizations to the Jetty distribution.
|
||||
`$JETTY_HOME`::
|
||||
* This is the location for the Jetty distribution binaries, default XML IoC configurations, and default module definitions.
|
||||
|
||||
____
|
||||
[IMPORTANT]
|
||||
Jetty Home should always be treated as a standard of truth.
|
||||
All configuration modifications, changes and additions should *always* be made in the appropriate Jetty Base directory.
|
||||
____
|
||||
|
||||
[[base-vs-home-resolution]]
|
||||
===== Eclipse Jetty Architecture: `$JETTY_HOME` and `$JETTY_BASE` Configuration Resolution
|
||||
|
||||
Potential configuration is resolved from these 2 directory locations.
|
||||
When Jetty starts up in processes configuration from them as follows:
|
||||
|
||||
Check Jetty Base First::
|
||||
If the referenced configuration exists, relative to the defined Jetty base, it is used.
|
||||
Check Jetty Home Second::
|
||||
If the referenced configuration exists, relative to the defined Jetty home, it is used.
|
||||
Use java.io.File(String pathname) Logic::
|
||||
Lastly, use the reference as a `java.io.File(String pathname)` reference, following the default resolution rules outlined by that constructor.In brief, the reference will be used as-is, be it relative (to current working directory, aka $\{user.dir}) or absolute path, or even network reference (such as on Windows and use of UNC paths).
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Control GCloud API classpath.
|
||||
Controls GCloud API classpath.
|
||||
|
||||
[tags]
|
||||
3rdparty
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Deploys the Hawtio console as a webapplication.
|
||||
Deploys the Hawtio console as a web application.
|
||||
|
||||
[tags]
|
||||
3rdparty
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Deploys the JAMon webapplication.
|
||||
Deploys the JAMon web application.
|
||||
|
||||
[tags]
|
||||
3rdparty
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Enables JSP for all webapplications deployed on the server.
|
||||
Enables JSP for all web applications deployed on the server.
|
||||
|
||||
[depend]
|
||||
servlet
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Enables JSTL for all webapplications deployed on the server.
|
||||
Enables JSTL for all web applications deployed on the server.
|
||||
|
||||
[depend]
|
||||
jsp
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Capture jakarta-commons-logging events and bridge them to SLF4J.
|
||||
Captures jakarta-commons-logging events and bridges them to SLF4J.
|
||||
|
||||
[tags]
|
||||
logging
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Capture java.util.logging events and bridge them to slf4j.
|
||||
Captures java.util.logging events and bridges them to slf4j.
|
||||
|
||||
[tags]
|
||||
logging
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Configure jetty logging to use Java Util Logging (jul).
|
||||
Configures jetty logging to use Java Util Logging (jul).
|
||||
SLF4J is used as the core logging mechanism.
|
||||
|
||||
[tags]
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Capture Apache log4j events and bridge them to SLF4J.
|
||||
Captures Apache log4j events and bridges them to SLF4J.
|
||||
|
||||
[tags]
|
||||
logging
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Configure jetty logging to use Log4j.
|
||||
Configures Jetty logging to use Log4j.
|
||||
SLF4J is used as the core logging mechanism.
|
||||
|
||||
[tags]
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Configure jetty logging to use log4j version 2.
|
||||
Configures Jetty logging to use log4j version 2.
|
||||
SLF4J is used as the core logging mechanism.
|
||||
|
||||
[tags]
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Configure jetty logging to use Logback Logging.
|
||||
Configures Jetty logging to use Logback Logging.
|
||||
SLF4J is used as the core logging mechanism.
|
||||
|
||||
[tags]
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Configure logging to use SLF4J No-Op Implementation.
|
||||
Configures Jetty logging to use SLF4J No-Op Implementation.
|
||||
|
||||
[tags]
|
||||
logging
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Configure logging to use SLF4J.
|
||||
Configures logging to use SLF4J.
|
||||
A specific implementation of SLF4J is not enabled.
|
||||
If one is not selected then NOP implementation will be used.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,9 +1,9 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Enables the unix setUID configuration.
|
||||
Enables the UNIX setUID configuration.
|
||||
The server may be started as root to open privileged ports/files before
|
||||
changing to a restricted user (eg jetty).
|
||||
changing to a restricted user (e.g. Jetty).
|
||||
|
||||
[depend]
|
||||
server
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
This module causes jetty to stop immediately after starting.
|
||||
This module causes Jetty to stop immediately after starting.
|
||||
This is good for testing configuration and/or precompiling quickstart webapps
|
||||
|
||||
[xml]
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Enable JAAS for deployed webapplications.
|
||||
Enables JAAS for deployed web applications.
|
||||
|
||||
[depend]
|
||||
server
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Enable JASPI authentication for deployed webapplications.
|
||||
Enables JASPI authentication for deployed web applications.
|
||||
|
||||
[depend]
|
||||
security
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Enables an unassembled maven webapp to run in a jetty distro.
|
||||
Enables an un-assembled Maven webapp to run in a Jetty distribution.
|
||||
|
||||
[depends]
|
||||
server
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Adds OpenId Connect authentication.
|
||||
Adds OpenId Connect authentication to the server.
|
||||
|
||||
[depend]
|
||||
security
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Enable the Jetty Proxy.
|
||||
Enables the Jetty Proxy service.
|
||||
Allows the server to act as a non-transparent proxy for browsers.
|
||||
|
||||
[depend]
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Enables the Jetty Quickstart module for rapid deployment of preconfigured webapplications.
|
||||
Enables the Jetty Quickstart module for rapid deployment of preconfigured web applications.
|
||||
|
||||
[depend]
|
||||
server
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
[description]
|
||||
Enables the jetty-rewrite handler.
|
||||
Specific rewrite rules must be added to either to etc/jetty-rewrite.xml or a custom xml/module
|
||||
Specific rewrite rules must be added to either to etc/jetty-rewrite.xml or a custom xml/module.
|
||||
|
||||
[tags]
|
||||
server
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Enable a server wide accept rate limit.
|
||||
Enables a server-wide accept rate limit.
|
||||
|
||||
[tags]
|
||||
connector
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Enable a server wide connection limit.
|
||||
Enables a server-wide connection limit.
|
||||
|
||||
[tags]
|
||||
connector
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Deprecated Debug Log using the DebugHandle.
|
||||
Deprecated Debug Log using DebugHandle.
|
||||
Replaced with the debug module.
|
||||
|
||||
[tags]
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Adds jar from $JETTY_HOME/lib/ext and $JETTY_BASE/lib/ext to the servers classpath.
|
||||
Adds the jar file from $JETTY_HOME/lib/ext and $JETTY_BASE/lib/ext to the server classpath.
|
||||
|
||||
[tags]
|
||||
classpath
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Enable GzipHandler for dynamic gzip compression for the entire server.
|
||||
Enables GzipHandler for dynamic gzip compression for the entire server.
|
||||
If MSIE prior to version 7 are to be handled, also enable the msie module.
|
||||
|
||||
[tags]
|
||||
|
|
|
|||
|
|
@ -2,8 +2,7 @@
|
|||
|
||||
[description]
|
||||
Enables an HTTP connector on the server.
|
||||
By default HTTP/1 is support, but HTTP2C can
|
||||
be added to the connector with the http2c module.
|
||||
By default HTTP/1 is support, but HTTP2C can be added to the connector by enabling the http2c module.
|
||||
|
||||
[tags]
|
||||
connector
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Enable the InetAccessHandler.
|
||||
Enables the InetAccessHandler.
|
||||
Applies a include/exclude control of the remote IP of requests.
|
||||
|
||||
[tags]
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Enable java.sql JPMS module.
|
||||
Enables the java.sql JPMS module.
|
||||
|
||||
[tags]
|
||||
jpms
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
A module that creates an ini template for setting JVM arguments (eg -Xmx ).
|
||||
Creates an ini template for setting JVM arguments (eg -Xmx ).
|
||||
|
||||
[ini-template]
|
||||
## JVM Configuration
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@
|
|||
[description]
|
||||
Enables a low resource monitor on the server.
|
||||
Can take actions if threads and/or connections
|
||||
cross configured threshholds.
|
||||
across configured threshholds.
|
||||
|
||||
[depend]
|
||||
server
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Log requests using CustomRequestLog and AsyncRequestLogWriter.
|
||||
Logs requests using CustomRequestLog and AsyncRequestLogWriter.
|
||||
|
||||
[tags]
|
||||
requestlog
|
||||
|
|
|
|||
|
|
@ -1,9 +1,10 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Enable session management.
|
||||
Enables session management.
|
||||
By enabling this module, it allows session management to be configured via the ini templates
|
||||
created or by enabling other session-cache or session-store modules. Without this module enabled,
|
||||
created or by enabling other session-cache or session-store modules.
|
||||
Without this module enabled,
|
||||
the server may still use sessions, but their management cannot be configured.
|
||||
|
||||
[tags]
|
||||
|
|
|
|||
|
|
@ -2,8 +2,7 @@
|
|||
|
||||
[description]
|
||||
Enables a TLS(SSL) Connector on the server.
|
||||
This may be used for HTTPS and/or HTTP2 by enabling
|
||||
the associated support modules.
|
||||
This may be used for HTTPS and/or HTTP2 by enabling the associated support modules.
|
||||
|
||||
[tags]
|
||||
connector
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Enable detailed statistics collection for the server.
|
||||
Enables detailed statistics collection for the server.
|
||||
|
||||
[tags]
|
||||
server
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
#
|
||||
# Thread Limit module
|
||||
# Applies ThreadLimiteHandler to entire server
|
||||
#
|
||||
|
||||
[description]
|
||||
Applies ThreadLimiteHandler to entire server
|
||||
|
||||
[tags]
|
||||
server
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Jetty utility servlets and filters available to a webapp.
|
||||
Adds Jetty utility servlets and filters available to a webapp.
|
||||
Puts org.eclipse.jetty.servlets on the server classpath (CGI, CrossOriginFilter, DosFilter,
|
||||
MultiPartFilter, PushCacheFilter, QoSFilter, etc.) for use by all webapplications.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Enable spring configuration processing of jetty XML files.
|
||||
All jetty style xml files can optionally be written as spring beans
|
||||
Enables Spring configuration processing of Jetty XML files.
|
||||
All Jetty-style XML files can optionally be written as Spring beans.2
|
||||
|
||||
[depend]
|
||||
server
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
[description]
|
||||
Allows Jetty to act as a web server.
|
||||
|
||||
[tag]
|
||||
server
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
[description]
|
||||
Redirects JVMs console stderr and stdout to a log file.
|
||||
includes output from Jetty's default StdErrLog logging.
|
||||
Includes output from Jetty's default StdErrLog logging.
|
||||
|
||||
[tags]
|
||||
logging
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Adds support for servlet specification webapplication to the server classpath.
|
||||
Without this, only Jetty specific handlers may be deployed.
|
||||
Adds support for servlet specification web applications to the server classpath.
|
||||
Without this, only Jetty-specific handlers may be deployed.
|
||||
|
||||
[depend]
|
||||
servlet
|
||||
|
|
|
|||
|
|
@ -203,6 +203,13 @@ public class WebDescriptor extends Descriptor
|
|||
redirectEntity("web-app_4_0.xsd", webapp40xsd);
|
||||
redirectEntity("http://xmlns.jcp.org/xml/ns/javaee/web-app_4_0.xsd", webapp40xsd);
|
||||
|
||||
// Handle linewrap hyphon error in PDF spec
|
||||
redirectEntity("webapp_4_0.xsd", webapp40xsd);
|
||||
redirectEntity("http://xmlns.jcp.org/xml/ns/javaee/webapp_4_0.xsd", webapp40xsd);
|
||||
|
||||
// handle jakartaee coordinates
|
||||
redirectEntity("http://xmlns.eclipse.org/xml/ns/jakartaee/web-app_4_0.xsd", webapp40xsd);
|
||||
|
||||
redirectEntity("web-fragment_3_0.xsd", webfragment30xsd);
|
||||
redirectEntity("http://java.sun.com/xml/ns/javaee/web-fragment_3_0.xsd", webfragment30xsd);
|
||||
redirectEntity("web-fragment_3_1.xsd", webfragment31xsd);
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Enable both jetty and javax websocket modules for deployed web applications.
|
||||
Enables both Jetty and javax websocket modules for deployed web applications.
|
||||
|
||||
[tags]
|
||||
websocket
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# DO NOT EDIT - See: https://www.eclipse.org/jetty/documentation/current/startup-modules.html
|
||||
|
||||
[description]
|
||||
Enable both jetty and javax websocket modules for deployed web applications.
|
||||
Enable both Jetty and javax websocket modules for deployed web applications.
|
||||
|
||||
[tags]
|
||||
websocket
|
||||
|
|
|
|||
Loading…
Reference in New Issue