From fbbc483234380e3779c4c0ab19e398f056cf2bbb Mon Sep 17 00:00:00 2001 From: calvincodes Date: Tue, 25 Aug 2020 19:15:59 -0700 Subject: [PATCH] Repharsing and using xref based links. Signed-off-by: calvincodes --- .../development/handlers/writing-custom-handlers.adoc | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/jetty-documentation/src/main/asciidoc/development/handlers/writing-custom-handlers.adoc b/jetty-documentation/src/main/asciidoc/development/handlers/writing-custom-handlers.adoc index 2f50d7c37b5..02c8a31b0ff 100644 --- a/jetty-documentation/src/main/asciidoc/development/handlers/writing-custom-handlers.adoc +++ b/jetty-documentation/src/main/asciidoc/development/handlers/writing-custom-handlers.adoc @@ -173,7 +173,9 @@ This is typically used to pass a request to a link:{JDURL}/org/eclipse/jetty/ser [[injecting-handlers]] ==== Injecting Handlers -A custom handler can be injected using an injection based XML: +The `Handler` needs to be added to the server classpath as described in xref:startup-classpath[]. +Then it can be added to the server, either by overriding some existing XML configuration files such as `jetty.xml` as shown below, or by defining a custom module as described in xref:custom-modules[]. + [source, xml] ---- @@ -187,10 +189,6 @@ A custom handler can be injected using an injection based XML: ---- -* The custom handler JAR should be available at `/path/to/myjettybase/lib/ext/` -* The custom handler XML should be available at `/path/to/myjettybase/etc/` -* The custom handler XML should be loaded into the jetty instance at the right point in the XML load order by declaring it to be used in a custom INI - [[more-about-handlers]] ==== More About Handlers