Update quickstart doco

This commit is contained in:
Jan Bartel 2020-10-07 13:18:11 +02:00
parent 9252afbbba
commit 8db68334e3
3 changed files with 6 additions and 4 deletions

View File

@ -31,5 +31,6 @@ include::deploy/chapter.adoc[]
include::protocols/chapter.adoc[]
include::keystore/chapter.adoc[]
include::modules/chapter.adoc[]
include::sessions/chapter.adoc[]
include::xml/chapter.adoc[]
include::sessions/chapter.adoc[]
include::quickstart/chapter.adoc[]

View File

@ -31,6 +31,7 @@ If you know Eclipse Jetty already, jump to a feature:
* xref:og-sessions[HTTP Session Caching and Clustering]
* xref:og-protocols-http2[HTTP/2 Support]
* xref:og-quickstart[Faster Web Application Deployment]
TODO

View File

@ -17,12 +17,12 @@
//
[[og-quickstart]]
=== Quickstart
=== Faster Web Application Deployment
The auto discovery features of the Servlet Specification can make deployments slow and uncertain.
Auto discovery of web application configuration can be useful during the development as it allows new features and frameworks to be enabled simply by dropping in a jar file.
However, for deployment, the need to scan the contents of many jars can have a significant impact at startup time.
However for production deployment, the need to scan the contents of many jars can have a significant impact at startup time.
The `quickstart` module allows a webapp to be pre-scanned, making startup predictable and faster.
During scanning all declarative configuration (ie from web.xml, web-fragment.xml and annotations) are encoded into an effective `web.xml`, called `WEB-INF/quickstart-web.xml`, which can be inspected to understand what will be deployed.
@ -30,7 +30,7 @@ NOTE:: Programmatic configuration is _not_ encoded into the generated `quickstar
With `quickstart`, webapps that took many seconds to scan and deploy can now be deployed in a few hundred milliseconds.
==== Enabling Quickstart
==== Enabling
Enable the `quickstart` module for your jetty base: