Sync documentation of main branch

Author: actions-user

_generated-doc/main/config/quarkus-all-config.adoc

@@ -4540,22 +4540,22 @@ endif::add-copy-button-to-env-var[]
 |boolean
 |`false`
 
-a|icon:lock[title=Fixed at build time] [[quarkus-core_quarkus-bootstrap-incubating-model-resolver]] [.property-path]##link:#quarkus-core_quarkus-bootstrap-incubating-model-resolver[`quarkus.bootstrap.incubating-model-resolver`]##
+a|icon:lock[title=Fixed at build time] [[quarkus-core_quarkus-bootstrap-legacy-model-resolver]] [.property-path]##link:#quarkus-core_quarkus-bootstrap-legacy-model-resolver[`quarkus.bootstrap.legacy-model-resolver`]##
 ifdef::add-copy-button-to-config-props[]
-config_property_copy_button:+++quarkus.bootstrap.incubating-model-resolver+++[]
+config_property_copy_button:+++quarkus.bootstrap.legacy-model-resolver+++[]
 endif::add-copy-button-to-config-props[]
 
 
 [.description]
 --
-A temporary option introduced to avoid a logging warning when `-Dquarkus.bootstrap.incubating-model-resolver` is added to the build command line. This option enables an incubating implementation of the Quarkus Application Model resolver. This option will be removed as soon as the incubating implementation becomes the default one.
+A temporary option introduced to avoid a logging warning when `-Dquarkus.bootstrap.legacy-model-resolver` is added to the build command line. This option enables the legacy implementation of the Quarkus Application Model resolver. This option will be removed once the legacy `ApplicationModel` resolver implementation gets removed.
 
 
 ifdef::add-copy-button-to-env-var[]
-Environment variable: env_var_with_copy_button:+++QUARKUS_BOOTSTRAP_INCUBATING_MODEL_RESOLVER+++[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_BOOTSTRAP_LEGACY_MODEL_RESOLVER+++[]
 endif::add-copy-button-to-env-var[]
 ifndef::add-copy-button-to-env-var[]
-Environment variable: `+++QUARKUS_BOOTSTRAP_INCUBATING_MODEL_RESOLVER+++`
+Environment variable: `+++QUARKUS_BOOTSTRAP_LEGACY_MODEL_RESOLVER+++`
 endif::add-copy-button-to-env-var[]
 --
 |boolean
@@ -61541,27 +61541,6 @@ endif::add-copy-button-to-env-var[]
 |boolean
 |`true`
 
-a|icon:lock[title=Fixed at build time] [[quarkus-messaging_quarkus-messaging-request-scoped-enabled]] [.property-path]##link:#quarkus-messaging_quarkus-messaging-request-scoped-enabled[`quarkus.messaging.request-scoped.enabled`]##
-ifdef::add-copy-button-to-config-props[]
-config_property_copy_button:+++quarkus.messaging.request-scoped.enabled+++[]
-endif::add-copy-button-to-config-props[]
-
-
-[.description]
---
-Whether to enable the RequestScope context on a message context
-
-
-ifdef::add-copy-button-to-env-var[]
-Environment variable: env_var_with_copy_button:+++QUARKUS_MESSAGING_REQUEST_SCOPED_ENABLED+++[]
-endif::add-copy-button-to-env-var[]
-ifndef::add-copy-button-to-env-var[]
-Environment variable: `+++QUARKUS_MESSAGING_REQUEST_SCOPED_ENABLED+++`
-endif::add-copy-button-to-env-var[]
---
-|boolean
-|`false`
-
 a|icon:lock[title=Fixed at build time] [[quarkus-messaging_quarkus-messaging-metrics-enabled]] [.property-path]##link:#quarkus-messaging_quarkus-messaging-metrics-enabled[`quarkus.messaging.metrics.enabled`]##
 ifdef::add-copy-button-to-config-props[]
 config_property_copy_button:+++quarkus.messaging.metrics.enabled+++[]

_generated-doc/main/config/quarkus-core_quarkus.bootstrap.adoc

@@ -91,22 +91,22 @@ endif::add-copy-button-to-env-var[]
 |boolean
 |`false`
 
-a|icon:lock[title=Fixed at build time] [[quarkus-core_quarkus-bootstrap-incubating-model-resolver]] [.property-path]##link:#quarkus-core_quarkus-bootstrap-incubating-model-resolver[`quarkus.bootstrap.incubating-model-resolver`]##
+a|icon:lock[title=Fixed at build time] [[quarkus-core_quarkus-bootstrap-legacy-model-resolver]] [.property-path]##link:#quarkus-core_quarkus-bootstrap-legacy-model-resolver[`quarkus.bootstrap.legacy-model-resolver`]##
 ifdef::add-copy-button-to-config-props[]
-config_property_copy_button:+++quarkus.bootstrap.incubating-model-resolver+++[]
+config_property_copy_button:+++quarkus.bootstrap.legacy-model-resolver+++[]
 endif::add-copy-button-to-config-props[]
 
 
 [.description]
 --
-A temporary option introduced to avoid a logging warning when `-Dquarkus.bootstrap.incubating-model-resolver` is added to the build command line. This option enables an incubating implementation of the Quarkus Application Model resolver. This option will be removed as soon as the incubating implementation becomes the default one.
+A temporary option introduced to avoid a logging warning when `-Dquarkus.bootstrap.legacy-model-resolver` is added to the build command line. This option enables the legacy implementation of the Quarkus Application Model resolver. This option will be removed once the legacy `ApplicationModel` resolver implementation gets removed.
 
 
 ifdef::add-copy-button-to-env-var[]
-Environment variable: env_var_with_copy_button:+++QUARKUS_BOOTSTRAP_INCUBATING_MODEL_RESOLVER+++[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_BOOTSTRAP_LEGACY_MODEL_RESOLVER+++[]
 endif::add-copy-button-to-env-var[]
 ifndef::add-copy-button-to-env-var[]
-Environment variable: `+++QUARKUS_BOOTSTRAP_INCUBATING_MODEL_RESOLVER+++`
+Environment variable: `+++QUARKUS_BOOTSTRAP_LEGACY_MODEL_RESOLVER+++`
 endif::add-copy-button-to-env-var[]
 --
 |boolean

_generated-doc/main/config/quarkus-messaging.adoc

@@ -49,27 +49,6 @@ endif::add-copy-button-to-env-var[]
 |boolean
 |`true`
 
-a|icon:lock[title=Fixed at build time] [[quarkus-messaging_quarkus-messaging-request-scoped-enabled]] [.property-path]##link:#quarkus-messaging_quarkus-messaging-request-scoped-enabled[`quarkus.messaging.request-scoped.enabled`]##
-ifdef::add-copy-button-to-config-props[]
-config_property_copy_button:+++quarkus.messaging.request-scoped.enabled+++[]
-endif::add-copy-button-to-config-props[]
-
-
-[.description]
---
-Whether to enable the RequestScope context on a message context
-
-
-ifdef::add-copy-button-to-env-var[]
-Environment variable: env_var_with_copy_button:+++QUARKUS_MESSAGING_REQUEST_SCOPED_ENABLED+++[]
-endif::add-copy-button-to-env-var[]
-ifndef::add-copy-button-to-env-var[]
-Environment variable: `+++QUARKUS_MESSAGING_REQUEST_SCOPED_ENABLED+++`
-endif::add-copy-button-to-env-var[]
---
-|boolean
-|`false`
-
 a|icon:lock[title=Fixed at build time] [[quarkus-messaging_quarkus-messaging-metrics-enabled]] [.property-path]##link:#quarkus-messaging_quarkus-messaging-metrics-enabled[`quarkus.messaging.metrics.enabled`]##
 ifdef::add-copy-button-to-config-props[]
 config_property_copy_button:+++quarkus.messaging.metrics.enabled+++[]

_generated-doc/main/config/quarkus-messaging_quarkus.messaging.adoc

@@ -49,27 +49,6 @@ endif::add-copy-button-to-env-var[]
 |boolean
 |`true`
 
-a|icon:lock[title=Fixed at build time] [[quarkus-messaging_quarkus-messaging-request-scoped-enabled]] [.property-path]##link:#quarkus-messaging_quarkus-messaging-request-scoped-enabled[`quarkus.messaging.request-scoped.enabled`]##
-ifdef::add-copy-button-to-config-props[]
-config_property_copy_button:+++quarkus.messaging.request-scoped.enabled+++[]
-endif::add-copy-button-to-config-props[]
-
-
-[.description]
---
-Whether to enable the RequestScope context on a message context
-
-
-ifdef::add-copy-button-to-env-var[]
-Environment variable: env_var_with_copy_button:+++QUARKUS_MESSAGING_REQUEST_SCOPED_ENABLED+++[]
-endif::add-copy-button-to-env-var[]
-ifndef::add-copy-button-to-env-var[]
-Environment variable: `+++QUARKUS_MESSAGING_REQUEST_SCOPED_ENABLED+++`
-endif::add-copy-button-to-env-var[]
---
-|boolean
-|`false`
-
 a|icon:lock[title=Fixed at build time] [[quarkus-messaging_quarkus-messaging-metrics-enabled]] [.property-path]##link:#quarkus-messaging_quarkus-messaging-metrics-enabled[`quarkus.messaging.metrics.enabled`]##
 ifdef::add-copy-button-to-config-props[]
 config_property_copy_button:+++quarkus.messaging.metrics.enabled+++[]

_versions/main/guides/maven-tooling.adoc

@@ -1057,6 +1057,9 @@ Here is a list of system properties the Quarkus bootstrap Maven resolver checks
 | `false`
 | By default, the Quarkus Maven resolver is reading project's POMs directly when discovering the project's layout. While in most cases it works well enough and relatively fast, reading raw POMs has its limitation. E.g. if a POM includes modules in a profile, these modules will not be discovered. This system property enables project's layout discovery based on the effective POM models, that are properly interpolated, instead of the raw ones. The reason this option is not enabled by default is it may appear to be significantly more time-consuming that could increase, e.g. CI testing times. Until there is a better approach found that could be used by default, projects that require it should enable this option.
 
+| `quarkus.bootstrap.legacy-model-resolver`
+| `false`
+| This *system* or *POM* property can be used to enable the legacy `ApplicationModel` resolver implementation. The property was introduced in Quarkus 3.19.0 and will be removed once the legacy implementation is known to be not in demand.
 |===
 
 These system properties above could be added to, e.g., a `surefire` and/or `failsafe` plugin configuration as

_versions/main/guides/messaging.adoc

@@ -562,7 +562,6 @@ public class StreamProcessor {
 }
 ----
 
-[[execution_model]]
 == Execution Model
 
 Quarkus Messaging sits on top of the xref:quarkus-reactive-architecture.adoc#engine[reactive engine] of Quarkus and leverages link:{eclipse-vertx}[Eclipse Vert.x] to dispatch messages for processing.
@@ -635,100 +634,6 @@ Depending on the broker technology, this can be useful to increase the applicati
 while still preserving the partial order of messages received in different copies.
 This is the case, for example, for Kafka, where multiple consumers can consume different topic partitions.
 
-== Context Propagation
-
-In Quarkus Messaging, the default mechanism for propagating context between different processing stages is the
-link:https://smallrye.io/smallrye-reactive-messaging/latest/concepts/message-context[message context].
-This provides a consistent way to pass context information along with the message as it flows through different stages.
-
-=== Interaction with Mutiny and MicroProfile Context Propagation
-
-Mutiny, which is the foundation of reactive programming in Quarkus, is integrated with the MicroProfile Context Propagation.
-This integration enables automatic capturing and restoring of context across asynchronous boundaries.
-To learn more about context propagation in Quarkus and Mutiny, refer to the xref:context-propagation.adoc[Context Propagation] guide.
-
-However, Quarkus Messaging needs to coordinate multiple asynchronous boundaries.
-This is why the default context propagation can result in unexpected behavior in some cases, especially using `Emitters`.
-
-To ensure consistent behavior, Quarkus Messaging disables the propagation of any context during message dispatching, through internal channels or connectors.
-This means that Emitters won't capture the caller context, and incoming channels won't dispatch messages by activating a context (ex. the request context).
-
-For example, you might want to propagate the caller context from an incoming HTTP request to the message processing stage.
-For emitters, instead of using the regular `Emitter` or `MutinyEmitter`, you can inject the `ContextualEmitter` to make sure the message captures the caller context.
-This ensures consistent and predictable behaviour by relying on the message context handling provided by the framework.
-
-For example, let `RequestScopedBean` a request-scoped bean, `ContextualEmitter` can be used to dispatch messages locally through the internal channel `app`:
-
-[source, java]
-----
-import jakarta.inject.Inject;
-import jakarta.ws.rs.Consumes;
-import jakarta.ws.rs.POST;
-import jakarta.ws.rs.Path;
-import jakarta.ws.rs.core.MediaType;
-
-import org.eclipse.microprofile.reactive.messaging.Channel;
-
-import io.quarkus.logging.Log;
-import io.quarkus.smallrye.reactivemessaging.runtime.ContextualEmitter;
-import io.smallrye.mutiny.Uni;
-import io.vertx.core.Context;
-import io.vertx.core.Vertx;
-
-@Path("/")
-public class Resource {
-
-    @Channel("app")
-    ContextualEmitter<String> emitter;
-
-    @Inject
-    RequestScopedBean requestScopedBean;
-
-    @POST
-    @Path("/send")
-    public void send(String message) {
-        requestScopedBean.setValue("Hello");
-        emitter.sendAndAwait(message);
-    }
-
-}
-----
-
-Then the request-scoped bean can be accessed in the message processing stage, regardless of the <<execution_model>>:
-
-[source, java]
-----
-import jakarta.enterprise.context.ApplicationScoped;
-import jakarta.inject.Inject;
-
-import org.eclipse.microprofile.reactive.messaging.Incoming;
-
-import io.quarkus.logging.Log;
-import io.smallrye.reactive.messaging.annotations.Blocking;
-
-
-@ApplicationScoped
-public class Processor {
-
-    @Inject
-    RequestScopedBean requestScopedBean;
-
-    @Incoming("app")
-    @Blocking
-    public void process(String message) {
-        Log.infof("Message %s from request %s", message, requestScopedBean.getValue());
-    }
-
-}
-----
-
-=== Request Context Activation
-
-In some cases, you might need to activate the request context while processing messages consumed from a broker.
-While using `@ActivateRequestContext` on the `@Incoming` method is an option, it's lifecycle does not follow that of a Quarkus Messaging message.
-For incoming channels, you can enable the request scope activation with the build time property `quarkus.messaging.request-scoped.enabled=true`.
-This will activate the request context for each message processed by the incoming channel, and close the context once the message is processed.
-
 == Health Checks
 
 Together with the SmallRye Health extension, Quarkus Messaging extensions provide health check support per channel.