summaryrefslogtreecommitdiffstats
path: root/jdisc_core
diff options
context:
space:
mode:
authorgjoranv <gv@verizonmedia.com>2021-11-10 10:23:25 +0100
committergjoranv <gv@verizonmedia.com>2021-11-10 16:13:53 +0100
commita8d87d56ffdde37354b37daf8460cc84fc59daba (patch)
tree852133a3478c15293b57fa5af2846f458b8a1be1 /jdisc_core
parent484143f7d3b1d53c2f34b7a3783d5a3538b9106b (diff)
JDK 17: Fix out-of-sequence javadoc headers.
Diffstat (limited to 'jdisc_core')
-rw-r--r--jdisc_core/src/main/java/com/yahoo/jdisc/application/package-info.java7
-rw-r--r--jdisc_core/src/main/java/com/yahoo/jdisc/handler/package-info.java4
-rw-r--r--jdisc_core/src/main/java/com/yahoo/jdisc/service/package-info.java2
3 files changed, 7 insertions, 6 deletions
diff --git a/jdisc_core/src/main/java/com/yahoo/jdisc/application/package-info.java b/jdisc_core/src/main/java/com/yahoo/jdisc/application/package-info.java
index a633e4bb291..950b3569319 100644
--- a/jdisc_core/src/main/java/com/yahoo/jdisc/application/package-info.java
+++ b/jdisc_core/src/main/java/com/yahoo/jdisc/application/package-info.java
@@ -3,7 +3,8 @@
* <p>Provides classes and interfaces for implementing an {@link com.yahoo.jdisc.application.Application
* Application}.</p>
*
- * <h3>Application</h3>
+ * <h2>Application</h2>
+ *
* <p>In every jDISC process there is exactly one Application instance, it is created during jDISC startup, and it is
* destroyed during jDISC shutdown. The Application uses the {@link com.yahoo.jdisc.application.ContainerBuilder
* ContainerBuilder} interface to load OSGi {@link org.osgi.framework.Bundle Bundles}, install Guice {@link
@@ -52,7 +53,7 @@ void reconfigureApplication() {
}
</pre>
*
- * <h3>Application and OSGi</h3>
+ * <h2>Application and OSGi</h2>
* <p>At the heart of jDISC is an OSGi framework. An Application is always packaged as an OSGi bundle. The OSGi
* technology itself is a set of specifications that define a dynamic component system for Java. These specifications
* enable a development model where applications are (dynamically) composed of many different (reusable) components. The
@@ -105,7 +106,7 @@ void reconfigureApplication() {
* into the application itself. Unless incompatible API changes are made to 3rd party jDISC components, it should be
* possible to upgrade dependencies without having to recompile and redeploy the Application.</p>
*
- * <h3>Application deployment</h3>
+ * <h2>Application deployment</h2>
* <p>jDISC allows a single binary to execute any application without having to change the command line parameters.
* Instead of
* modifying the parameters of the single application binary, changing the application is achieved by setting a single
diff --git a/jdisc_core/src/main/java/com/yahoo/jdisc/handler/package-info.java b/jdisc_core/src/main/java/com/yahoo/jdisc/handler/package-info.java
index 1b08ef5e60c..088c9d5592d 100644
--- a/jdisc_core/src/main/java/com/yahoo/jdisc/handler/package-info.java
+++ b/jdisc_core/src/main/java/com/yahoo/jdisc/handler/package-info.java
@@ -3,7 +3,7 @@
* <p>Provides classes and interfaces for implementing a {@link com.yahoo.jdisc.handler.RequestHandler
* RequestHandler}.</p>
*
- * <h3>RequestHandler</h3>
+ * <h2>RequestHandler</h2>
* <p>All {@link com.yahoo.jdisc.Request Requests} in a jDISC application are processed by RequestHandlers. These are
* components created by the {@link com.yahoo.jdisc.application.Application Application}, and bound to one or more URI
* patterns through the {@link com.yahoo.jdisc.application.ContainerBuilder ContainerBuilder} API. Upon receiving a
@@ -39,7 +39,7 @@ MyApplication(ContainerActivator activator, CurrentContainer container) {
* otherwise, a jDISC application that is intended to forward large streams of data can do so without having to make any
* copies of that data as it is passing through.</p>
*
- * <h3>ResponseHandler</h3>
+ * <h2>ResponseHandler</h2>
* <p>The complement of the Request is the Response. A Response is a numeric status code and a set of header fields.
* Just as Requests are processed by RequestHandlers, Responses are processed by ResponseHandlers. The ResponseHandler
* interface is fully asynchronous, and uses the ContentChannel class to encapsulate the asynchronous passing of
diff --git a/jdisc_core/src/main/java/com/yahoo/jdisc/service/package-info.java b/jdisc_core/src/main/java/com/yahoo/jdisc/service/package-info.java
index 532d2921469..cc2cd4abbef 100644
--- a/jdisc_core/src/main/java/com/yahoo/jdisc/service/package-info.java
+++ b/jdisc_core/src/main/java/com/yahoo/jdisc/service/package-info.java
@@ -3,7 +3,7 @@
* <p>Provides classes and interfaces for implementing a {@link com.yahoo.jdisc.service.ClientProvider ClientProvider} or
* a {@link com.yahoo.jdisc.service.ServerProvider ServerProvider}.</p>
*
- * <h3>ServerProvider</h3>
+ * <h2>ServerProvider</h2>
* <p>All {@link com.yahoo.jdisc.Request Requests} that are processed in a jDISC application are created by
* ServerProviders. These are components created by the {@link com.yahoo.jdisc.application.Application Application}, and
* they are the parts of jDISC that accept incoming connections. The ServerProvider creates and dispatches Request