Sync web site with Quarkus documentation

Author: quarkusbot

_guides/_attributes.adoc

@@ -1,7 +1,7 @@
 // Common attributes.
 // --> No blank lines (it ends the document header)
 :project-name: Quarkus
-:quarkus-version: 3.26.1
+:quarkus-version: 3.26.2
 :quarkus-platform-groupid: io.quarkus.platform
 // .
 :maven-version: 3.9.9
@@ -11,13 +11,13 @@
 :mandrel-flavor: jdk-21
 :surefire-version: 3.5.3
 :gradle-version: 9.0.0
-:elasticsearch-version: 9.1.2
-:elasticsearch-image: docker.io/elastic/elasticsearch:9.1.2
+:elasticsearch-version: 9.1.3
+:elasticsearch-image: docker.io/elastic/elasticsearch:9.1.3
 :opensearch-image: docker.io/opensearchproject/opensearch:3.1.0
 :infinispan-version: ${infinispan.version}
 :infinispan-protostream-version: ${infinispan.protostream.version}
-:logstash-image: docker.io/elastic/logstash:9.1.2
-:kibana-image: docker.io/elastic/kibana:9.1.2
+:logstash-image: docker.io/elastic/logstash:9.1.3
+:kibana-image: docker.io/elastic/kibana:9.1.3
 :keycloak-docker-image: quay.io/keycloak/keycloak:26.3.0
 :jandex-version: 3.4.0
 :jandex-gradle-plugin-version: 1.0.0

_guides/assistant.adoc

@@ -257,7 +257,7 @@ To use this state in your page:
 import { observeState } from 'lit-element-state'; // <1>
 import { assistantState } from 'assistant-state'; // <2>
 
-export class QwcExtentionPage extends observeState(LitElement) {  // <3>
+export class QwcExtensionPage extends observeState(LitElement) {  // <3>
 ----
 <1> import observeState from the LitState library.
 <2> import the state you are interested in, in this case assistant state.

_guides/command-mode-reference.adoc

@@ -248,7 +248,17 @@ public class HelloIT extends HelloTest {
 }
 ----
 
-=== Mocking
+=== Limitations
+
+`@QuarkusMainTest` does **not** support the following features:
+
+- Injection of CDI beans
+- Using Panache entities
+- Using mocks with `@InjectMock`
+
+Usually, it's best to use a combination of `@QuarkusMainTest` tests for testing application externals, and `@QuarkusTest` tests for fine-grained testing which requires access to application internals.
+
+==== Mocking
 
 CDI injection is not supported in the `@QuarkusMainTest` tests.
 Consequently, mocking CDI beans with `QuarkusMock` or `@InjectMock` is not supported either.

_guides/config-reference.adoc

@@ -12,8 +12,6 @@ include::_attributes.adoc[]
 :sectnumlevels: 4
 :topics: configuration
 
-IMPORTANT: The content of this guide has been revised and split into additional topics. Please check the <<additional-information,Additional Information>> section.
-
 In this reference guide we're going to describe various aspects of Quarkus configuration. A Quarkus application and
 Quarkus itself (core and extensions) are both configured via the same mechanism that leverages
 the https://github.com/smallrye/smallrye-config[SmallRye Config] API an implementation of the
@@ -195,9 +193,80 @@ Quarkus provides additional extensions which cover other configuration formats a
 
 TIP: It is also possible to create a xref:config-extending-support.adoc#custom-config-source[Custom Config Source].
 
-== Inject
+== ConfigMapping
+
+The recommended way to expose configuration to a Quarkus application is by mapping it with an interface. With
+https://smallrye.io/smallrye-config/Main/config/mappings/[SmallRye Config Mappings], it is possible to
+group multiple configuration properties in a single interface that share the same prefix (or namespace). It supports
+the following set of features:
+
+* Automatic conversion of the configuration type, including List, Set, Map, Optional, and primitive types.
+* Nested Config Mapping groups.
+* Configuration Properties Naming Strategies
+* Integration with Bean Validation
 
-Quarkus uses https://microprofile.io/project/eclipse/microprofile-config[MicroProfile Config] annotations to inject the
+A Config Mapping requires an interface with minimal metadata configuration annotated with
+`@io.smallrye.config.ConfigMapping`:
+
+[source,java]
+----
+@ConfigMapping(prefix = "server")
+public interface Server {
+    String host();
+
+    int port();
+
+    int sslPort();
+}
+----
+
+A complex object type uses the following rules to map configuration values to their member values:
+
+* A configuration path is built by taking the object type prefix (or namespace) and the mapping member name
+* The member name is converted to its kebab-case format
+* If the member name is represented as a getter, the member name is taken from its property name equivalent, and then
+converted to its kebab-case format.
+* The configuration value is automatically converted to the member type
+* The configuration path is required to exist with a valid configuration value or the mapping will fail.
+
+NOTE: Kebab-case - the method name is derived by replacing case changes with a dash to map the configuration property.
+
+The `Server` interface can map configuration properties with the name `server.host` into the `Server.host()`
+method, `server.port` into `Server.port()` method, and `server.ssl-port` into `Server.sslPort()` method. The
+configuration property name to look up is constructed from the prefix and the method name (in kebab-case), separated
+by adot (`.`) character.
+
+A `@ConfigMapping` can be injected into any CDI aware bean:
+
+[source,java]
+----
+@ApplicationScoped
+class BusinessBean {
+    @Inject
+    Server server;
+
+    void businessMethod() {
+        String host = server.host();
+    }
+}
+----
+
+For non-CDI components, use the `io.smallrye.config.SmallRyeConfig#getConfigMapping` API to retrieve the config mapping
+instance:
+
+[source,java]
+----
+SmallRyeConfig config = ConfigProvider.getConfig().unwrap(SmallRyeConfig.class);
+Server server = config.getConfigMapping(Server.class);
+----
+
+TIP: Check the xref:config-mappings.adoc[Mapping configuration to objects] guide for advanced usages with
+`@ConfigMapping`.
+
+== ConfigProperty
+
+While `@ConfigMapping` is the recommended approach, Quarkus also supports
+https://microprofile.io/project/eclipse/microprofile-config[MicroProfile Config] annotations to inject the
 configuration properties in the application.
 
 [source,java]
@@ -221,19 +290,20 @@ String suffix;
 @ConfigProperty(name = "greeting.name")
 Optional<String> name; <3>
 ----
-<1> If you do not provide a value for this property, the application startup fails with `jakarta.enterprise.inject.spi.DeploymentException: No config value of type [class java.lang.String] exists for: greeting.message`.
+<1> If you do not provide a value for this property, the application startup fails with
+`io.quarkus.runtime.configuration.ConfigurationException: Failed to load config value of type class java.lang.String for: greeting.messagee`.
 <2> The default value is injected if the configuration does not provide a value for `greeting.suffix`.
 <3> This property is optional - an empty `Optional` is injected if the configuration does not provide a value for `greeting.name`.
 
 TIP: Use xref:config-mappings.adoc#config-mappings[Config Mappings] to group similar configuration properties.
 
-=== Default Values
+== Default Values
 
-If a property is associated with a default value (by way of the `defaultValue` attribute), and no configuration value
-is supplied for the property, then rather than throwing a `jakarta.enterprise.inject.spi.DeploymentException`, the
-default value will be used. The `defaultValue` value is expressed as a `String`, and uses the same conversion mechanism
-used to process configuration values. Several Built-in Converters already exist for primitives, boxed primitives, and
-other classes; for example:
+If a configuration is associated with a default value (by way of the `io.smallrye.config.WithDefault` or
+`org.eclipse.microprofile.config.inject.ConfigProperty.defaultValue`), and no configuration value is supplied for the
+property, then rather than throwing an exception, the default value will be used. A default value is expressed as a
+`String`, and uses the same conversion mechanism used to process configuration values. Several Built-in Converters
+already exist for primitives, boxed primitives, and other classes; for example:
 
 * Primitives: `boolean`, `byte`, `short`, etc.
 * Boxed primitives: `java.lang.Boolean`, `java.lang.Byte`, `java.lang.Short`, etc.
@@ -248,10 +318,10 @@ these converters comply with the Microprofile or custom implementation providers
 * Boolean values will be `true` in cases "true", "1", "YES", "Y" "ON". Otherwise, value will be interpreted as false
 * For float and double values the fractional digits must be separated by a dot `.`
 
-Note that when a combination of `Optional*` types and the `defaultValue` attribute are used, the defined `defaultValue`
-will still be used and if no value is given for the property, the `Optional*` will be present and populated with the
-converted default value. However, when the property is explicitly empty, the default value is not used and the
-`Optional` will be empty. Consider this example:
+Note that when a combination of `Optional*` types and defaults are used, the defined default value will still be used
+and if no value is given for the property, the `Optional*` will be present and populated with the converted default
+value. However, when the property is explicitly empty, the default value is not used and the `Optional` will be empty.
+Consider this example:
 
 [source,properties]
 ----
@@ -274,23 +344,16 @@ greeting.suffix=
 will result in a `java.util.NoSuchElementException: SRCFG02004: Required property greeting.message not found` on
 startup and the default value will not be assigned.
 
-Below is an example of a Quarkus-supplied converter:
-
-[source,java]
-----
-@ConfigProperty(name = "server.address", defaultValue = "192.168.1.1")
-InetAddress serverAddress;
-----
-
 == Programmatically access
 
-The `org.eclipse.microprofile.config.ConfigProvider.getConfig()` API allows to access the Config API programmatically.
+The `io.smallrye.config.SmallRyeConfig` API allows to access the Config API programmatically.
 This API is mostly useful in situations where CDI injection is not available.
 
 [source,java]
 ----
-String databaseName = ConfigProvider.getConfig().getValue("database.name", String.class);
-Optional<String> maybeDatabaseName = ConfigProvider.getConfig().getOptionalValue("database.name", String.class);
+SmallRyeConfig config = org.eclipse.microprofile.config.ConfigProvider.getConfig().unwrap(SmallRyeConfig.class);
+String databaseName = config.getValue("database.name", String.class);
+Optional<String> maybeDatabaseName = config.getOptionalValue("database.name", String.class);
 ----
 
 IMPORTANT: Do not use `System.getProperty(String)` or `System.getEnv(String)` to retrieve configuration values. These
@@ -496,17 +559,6 @@ Multiple profiles priority work in reverse order. With `quarkus.profile=common,d
 profile and then the `common` profile.
 ====
 
-=== Default Runtime Profile
-
-The default Quarkus runtime profile is set to the profile used to build the application:
-
-[source,bash]
-----
-./mvnw package -Dnative -Dquarkus.profile=prod-aws
-./target/my-app-1.0-runner // <1>
-----
-<1> The command will run with the `prod-aws` profile. This can be overridden using the `quarkus.profile` configuration.
-
 [[property-expressions]]
 == Property Expressions
 
@@ -674,19 +726,51 @@ extensions. Therefore, the `quarkus.` prefix should **never** be used for applic
 
 === Build Time configuration
 
-Some Quarkus configurations only take effect during build time, meaning it is not possible to change them at runtime. These
-configurations are still available at runtime but as read-only and have no effect in Quarkus behaviour. A change to any
-of these configurations requires a rebuild of the application itself to reflect changes of such properties.
+Some Quarkus configurations only take effect during build time (compile), meaning it is not possible to change it at
+runtime. These configurations are still available at runtime but as read-only and have no effect in Quarkus
+behaviour. A change to any of these configurations requires a rebuild of the application itself to reflect changes of
+such properties. This allows Quarkus to provide optimizations and reduce complexity based on the current build
+configuration. By default, Quarkus uses the `prod` configuration profile to build the application.
 
 TIP: The properties fixed at build time are marked with a lock icon (icon:lock[]) in the xref:all-config.adoc[list of all configuration options].
 
 However, some extensions do define properties _overridable at runtime_. A simple example is the database URL, username
 and password which is only known specifically in your target environment, so they can be set and influence the
 application behaviour at runtime.
 
-== Change build time properties after your application has been published
+=== Config Recording
+
+During the build process, Quarkus proceeds to record the available configuration in the final binary, to ensure it can
+start successfully in runtime, without missing required configuration. The following sources are excluded from
+recording:
+
+* System Properties
+* Environment Variables
+* `.env`
+* Build System Sources (provided by Maven or Gradle)
+
+=== Default Runtime Profile
+
+The default Quarkus runtime profile is set to the profile used to build the application:
+
+[source,bash]
+----
+./mvnw package -Dnative -Dquarkus.profile=prod-aws
+./target/my-app-1.0-runner // <1>
+----
+<1> The command will run with the `prod-aws` profile. This can be overridden using the `quarkus.profile` configuration.
+
+[IMPORTANT]
+====
+Using a different configuration profile at runtime from the one used to build the application can lead to unexpected
+results.
+====
+
+== Change configuration after build (Reaugmentation)
 
-If you are in the rare situation that you need to change the build time configuration after your application is built, then check out how xref:reaugmentation.adoc[re-augmentation] can be used to rebuild the augmentation output for a different build time configuration.
+If you are in the rare situation that you need to change the build time configuration after your application is built,
+then check out how xref:reaugmentation.adoc[re-augmentation] can be used to rebuild the augmentation output for a
+different build time configuration.
 
 == Tracking effective build time configuration used at build time
 

_guides/dev-ui.adoc

@@ -872,7 +872,7 @@ To use this state in your page:
 import { observeState } from 'lit-element-state'; // <1>
 import { connectionState } from 'connection-state'; // <2>
 
-export class QwcExtentionPage extends observeState(LitElement) {  // <3>
+export class QwcExtensionPage extends observeState(LitElement) {  // <3>
 ----
 <1> import observeState from the LitState library.
 <2> import the state you are interested in, in this case connection state.
@@ -900,7 +900,7 @@ To use this state in your page:
 import { observeState } from 'lit-element-state'; // <1>
 import { themeState } from 'theme-state'; // <2>
 
-export class QwcExtentionPage extends observeState(LitElement) {  // <3>
+export class QwcExtensionPage extends observeState(LitElement) {  // <3>
 ----
 <1> import observeState from the LitState library.
 <2> import the state you are interested in, in this case theme state.
@@ -934,7 +934,7 @@ To use this state in your page:
 import { observeState } from 'lit-element-state'; // <1>
 import { assistantState } from 'assistant-state'; // <2>
 
-export class QwcExtentionPage extends observeState(LitElement) {  // <3>
+export class QwcExtensionPage extends observeState(LitElement) {  // <3>
 ----
 <1> import observeState from the LitState library.
 <2> import the state you are interested in, in this case assistant state.

_guides/opentelemetry-metrics.adoc

@@ -362,9 +362,9 @@ IMPORTANT: Each unique combination of metric name and dimension produces a uniqu
 Using an unbounded set of dimensional data (many different values like a userId) can lead to a "cardinality explosion", an exponential increase in the creation of new time series.
 Avoid!
 
-OpenTelemetry provides many other types of Counters: `LongUpDownCounter`, `DoubleCounter`, `DoubleUpDownCounter` and also Observable, async counters like `ObservableLongCounter`, `ObservableDoubleCounter`, `ObservableLongUpDownCounter` and `ObservableDoubleUpDownCounter`.
+OpenTelemetry provides many other types of Counters: `LongUpDownCounter`, `DoubleCounter`, `UpDownCounter`,  `DoubleUpDownCounter` and also Observable, async counters like `ObservableLongCounter`, `ObservableDoubleCounter`, `ObservableLongUpDownCounter` and `ObservableDoubleUpDownCounter`.
 
-For more details please refer to the https://opentelemetry.io/docs/languages/java/instrumentation/#using-counters[OpenTelemetry Java documentation about Counters].
+For more details please refer to the https://opentelemetry.io/docs/languages/java/api/#counter[OpenTelemetry Java documentation about Counters].
 
 === Gauges
 Observable Gauges should be used to measure non-additive values.

_guides/opentelemetry.adoc

@@ -398,7 +398,7 @@ You can also use the xref:logging-exporter-for-debugging[logging exporter] to ou
 
 Quarkus supports the OpenTelemetry Autoconfiguration for Traces.
 The configurations match what you can see at
-https://github.com/open-telemetry/opentelemetry-java/blob/main/sdk-extensions/autoconfigure/README.md[OpenTelemetry SDK Autoconfigure]
+https://opentelemetry.io/docs/languages/java/configuration/[OpenTelemetry SDK Autoconfigure]
 adding the usual `quarkus.*` prefix.
 
 Quarkus OpenTelemetry configuration properties now have the `quarkus.otel.*` prefix.

_guides/rest.adoc

@@ -917,6 +917,15 @@ See <<execution-model,Execution Model documentation>> for more information.
 The link:{jdkapi}/java/util/concurrent/CompletionStage.html[`CompletionStage`] return
 type is also supported.
 
+==== Request cancellation
+
+Async endpoints that return `Uni` support request cancellation, which means that if the underlying HTTP connection is closed for whatever reason,
+the request pipeline defined by the returned `Uni` is also cancelled. This can be very useful in avoiding unnecessary work on the server
+when the client isn't going to use the response anyway.
+
+If instead of cancelling the pipeline, it should be completed regardless of the state of the HTTP connection, Quarkus REST provides the `org.jboss.resteasy.reactive.server.Cancellable` annotation
+which can be applied to REST classes or methods to control the cancellation behavior.
+
 === Streaming support
 
 If you want to stream your response element by element, you can make your endpoint method return a