[RESTEASY-2406] Port use of Microprofile Config to 3.x

docbook/reference/en/en-US/modules/Async_job_service.xml

@@ -61,7 +61,8 @@ POST http://example.com/myservice?oneway=true
    </sect1>
    <sect1 id="async_job_setup">
      <title>Setup and Configuration</title>
-     <para>You must enable the Asynchronous Job Service in your web.xml file as it is not turned on by default.</para>
+     <para>You must enable the Asynchronous Job Service, as it is not turned on by default. If the relevant configuration properties are configured
+     in web.xml, it would look like the following: </para>
 <programlisting>
 <![CDATA[
 <web-app>
@@ -102,5 +103,7 @@ POST http://example.com/myservice?oneway=true
 </web-app>
 ]]>
 </programlisting>
+
+   <para>See <xref linkend="microprofile_config"/> for more information about application configuration.</para>
    </sect1>
 </chapter>

docbook/reference/en/en-US/modules/Cache_NoCache_CacheControl.xml

@@ -130,7 +130,7 @@ public static void main(String[] args) throws Exception
           via your Application getSingletons() or getClasses() methods.  The underlying cache is Infinispan.  By default,
           RESTEasy will create an Infinispan cache for you.  Alternatively, you can create and pass in an instance
           of your cache to the ServerCacheFeature constructor.  You can also configure Infinispan by specifying
-          various context-param variables in your web.xml.  First, if you are using Maven you must depend on the resteasy-cache-core artifact:</para>
+          various parameters.  First, if you are using Maven you must depend on the resteasy-cache-core artifact:</para>
 <programlisting>
 <![CDATA[
 <dependency>
@@ -140,7 +140,7 @@ public static void main(String[] args) throws Exception
 </dependency>
 ]]>
 </programlisting>
-      <para>The next thing you should probably do is set up the Infinispan configuration in your web.xml.</para>
+      <para>The next thing you should probably do is set up the Infinispan configuration. In your web.xml, it would look like</para>
 <programlisting>
 <![CDATA[
 <web-app>
@@ -161,6 +161,9 @@ public static void main(String[] args) throws Exception
        server.request.cache.infinispan.config.file can either be a classpath or a file path. server.request.cache.infinispan.cache.name
        is the name of the cache you want to reference that is declared in the config file.
    </para>
+
+   <para>See <xref linkend="microprofile_config"/> for more information about application configuration. </para>
+
    </sect1>
    <sect1 id="Http_Precondition">
         <title>HTTP preconditions</title>
@@ -173,7 +176,8 @@ public static void main(String[] args) throws Exception
         <para>
             By default RESTEasy will return status code 304 (Not modified) or 412 (Precondition failed) if any of conditions fails.
             However it is not compliant with RFC 7232 which states that headers <literal>"If-Match"</literal>, <literal>"If-None-Match"</literal> MUST have higher precedence.
-            You can enable RFC 7232 compatible mode by setting <literal>resteasy.rfc7232preconditions</literal> context parameter to <literal>true</literal>
+            You can enable RFC 7232 compatible mode by setting the parameter <literal>resteasy.rfc7232preconditions</literal> to <literal>true</literal>.
+            See <xref linkend="microprofile_config"/> for more information about application configuration.
         </para>
    </sect1>
 </chapter>

docbook/reference/en/en-US/modules/Content_Marshalling_Providers.xml

@@ -365,25 +365,27 @@ public class MultipartProvider implements MessageBodyReader {
 
          By default, RESTEasy's built-in unmarshaller for org.w3c.dom.Document documents will not expand external entities,
          replacing them by the empty string instead. It can be configured to replace external entities by values defined in the
-         DTD by setting the context parameter
+         DTD by setting the parameter
 
       </para>
 
       <blockquote>resteasy.document.expand.entity.references</blockquote>
 
-      <para> to "true" in the web.xml file:</para>
+      <para> to "true". If configured in the web.xml file, it would be:</para>
 
 <programlisting>
 &lt;context-param&gt;
     &lt;param-name&gt;resteasy.document.expand.entity.references&lt;/param-name&gt;
     &lt;param-value&gt;true&lt;/param-value&gt;
 &lt;/context-param&gt;
 </programlisting>
-
+
+      <para>See <xref linkend="microprofile_config"/> for more information about application configuration. </para>
+
       <para>
 
       Another way of dealing with the problem is by prohibiting DTDs, which RESTEasy does by default. This behavior
-      can be changed by setting the context parameter
+      can be changed by setting the parameter
 
       </para>
 
@@ -412,7 +414,7 @@ public class MultipartProvider implements MessageBodyReader {
    then the expansion of &amp;foo6; 
    would result in 1,000,000 foos. By default, RESTEasy will limit the number of expansions and
    the number of attributes per entity. The exact behavior depends on the underlying parser. The limits
-   can be turned off by setting the context parameter
+   can be turned off by setting the parameter
    </para>
 
    <blockquote>resteasy.document.secure.processing.feature</blockquote>
@@ -450,7 +452,7 @@ with an appropriate charset value.
    charset parameter to the Content-Type response header. RESTEasy started adding the explicit charset
    parameter in releases 3.1.2.Final and 3.0.22.Final, and that new behavior could cause some compatibility problems. To
    specify the previous behavior, in which UTF-8 was used for text media types, but the explicit charset
-   was not appended, the context parameter "resteasy.add.charset" may be set to "false". It defaults to "true".
+   was not appended, the parameter "resteasy.add.charset" may be set to "false". It defaults to "true".
    </para>
 
    <para>

docbook/reference/en/en-US/modules/ExceptionMappers.xml

@@ -56,8 +56,8 @@
    </para>
    <para>
 
-      You register ExceptionMappers the same way you do MessageBodyReader/Writers. By scanning, through the resteasy
-      provider context-param (if you're deploying via a WAR file), or programmatically through the
+      You register ExceptionMappers the same way you do MessageBodyReader/Writers, by scanning for @Provider
+      annotated classes, or programmatically through the
       ResteasyProviderFactory class.
    </para>
    <para>