Sync documentation of main branch

Author: actions-user

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

@@ -79368,7 +79368,7 @@ Environment variable: `+++QUARKUS_DATASOURCE_REACTIVE_CACHE_PREPARED_STATEMENTS+
 endif::add-copy-button-to-env-var[]
 --
 |boolean
-|`+++false+++`
+|`+++true for PostgreSQL/MySQL/MariaDB/Db2, false otherwise+++`
 
 a| [[quarkus-reactive-datasource_quarkus-datasource-reactive-url]] [.property-path]##link:#quarkus-reactive-datasource_quarkus-datasource-reactive-url[`quarkus.datasource.reactive.url`]##
 ifdef::add-copy-button-to-config-props[]

_generated-doc/main/config/quarkus-reactive-datasource.adoc

@@ -57,7 +57,7 @@ Environment variable: `+++QUARKUS_DATASOURCE_REACTIVE_CACHE_PREPARED_STATEMENTS+
 endif::add-copy-button-to-env-var[]
 --
 |boolean
-|`+++false+++`
+|`+++true for PostgreSQL/MySQL/MariaDB/Db2, false otherwise+++`
 
 a| [[quarkus-reactive-datasource_quarkus-datasource-reactive-url]] [.property-path]##link:#quarkus-reactive-datasource_quarkus-datasource-reactive-url[`quarkus.datasource.reactive.url`]##
 ifdef::add-copy-button-to-config-props[]

_generated-doc/main/config/quarkus-reactive-datasource_quarkus.datasource.adoc

@@ -57,7 +57,7 @@ Environment variable: `+++QUARKUS_DATASOURCE_REACTIVE_CACHE_PREPARED_STATEMENTS+
 endif::add-copy-button-to-env-var[]
 --
 |boolean
-|`+++false+++`
+|`+++true for PostgreSQL/MySQL/MariaDB/Db2, false otherwise+++`
 
 a| [[quarkus-reactive-datasource_quarkus-datasource-reactive-url]] [.property-path]##link:#quarkus-reactive-datasource_quarkus-datasource-reactive-url[`quarkus.datasource.reactive.url`]##
 ifdef::add-copy-button-to-config-props[]

_versions/main/guides/rest.adoc

@@ -778,6 +778,34 @@ public class Endpoint {
 NOTE: You can also use the Jakarta REST type link:{jaxrsapi}/jakarta/ws/rs/core/Response.html[`Response`] but it is
 not strongly typed to your entity.
 
+==== Responding with files
+
+When a file needs to be returned, the following code ensures that Quarkus properly streams the file contents to the client.
+
+[source,java]
+----
+package org.acme.rest;
+
+import jakarta.ws.rs.GET;
+import jakarta.ws.rs.Path;
+import org.jboss.resteasy.reactive.RestResponse;
+import org.jboss.resteasy.reactive.RestResponse.ResponseBuilder;
+
+@Path("")
+public class Endpoint {
+
+    @Path("file")
+    @GET
+    public RestResponse<java.nio.file.Path> largePathRestResponse() throws IOException {
+        java.nio.file.Path path = ...
+
+        return RestResponse.ResponseBuilder.ok(path)
+                .header(HttpHeaders.CONTENT_DISPOSITION, "some-file-name")
+                .build();
+    }
+}
+----
+
 ==== Using annotations
 
 Alternatively, if you only need to set the status code and / or HTTP headers with static values, you can use `@org.jboss.resteasy.reactive.ResponseStatus` and /or `ResponseHeader` respectively.

_versions/main/guides/spring-web.adoc

@@ -469,6 +469,46 @@ The following parameter types are supported, in arbitrary order:
 
 Other parameter types mentioned in the Spring `https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/web/bind/annotation/ExceptionHandler.html[ExceptionHandler javadoc]` are not supported.
 
+==== Using `HttpServerRequest` and `HttpServerResponse` in Spring Web-style exception handlers
+
+When using the Quarkus Spring Web compatibility layer on top of the reactive stack (`quarkus-rest-jackson`),
+you cannot inject servlet-based request and response types such as `jakarta.servlet.http.HttpServletRequest` or `jakarta.servlet.http.HttpServletResponse`.
+These types are only available when using the Classic RESTEasy stack (quarkus-resteasy / quarkus-resteasy-jackson), which relies on the Servlet API provided by `quarkus-undertow` dependency.
+
+To provide a Spring-friendly experience while staying reactive, Quarkus allows you to inject the following types into your `@ExceptionHandler` methods:
+
+- io.vertx.core.http.HttpServerRequest
+
+- io.vertx.core.http.HttpServerResponse
+
+These types give you direct access to the underlying Vert.x HTTP layer.
+This allows you to manipulate the response (e.g. set headers, cookies, or status codes) or enrich the returned information using details from the request.
+
+For example:
+
+[source, java]
+----
+@ExceptionHandler(IllegalArgumentException.class)
+public ResponseEntity<Object> handleException(Exception ex,
+                                                       HttpServerRequest request,
+                                                       HttpServerResponse response) {
+    // Add a custom header to the response
+    response.putHeader("X-Error-Reason", "IllegalArgument");
+
+    // Build a response body enriched with request details
+    String body = String.format("Request %s %s failed",
+            request.method().name(),
+            request.uri());
+
+    return new ResponseEntity<>(body, HttpStatus.BAD_REQUEST);
+}
+
+----
+
+**Warning:** This is potentially dangerous.
+Users should only do this if they understand the reactive model, and are aware that writing directly to the response can bypass normal handling of status codes, headers, and serialization.
+
+
 == Important Technical Note
 
 Please note that the Spring support in Quarkus does not start a Spring Application Context nor are any Spring infrastructure classes run.