Sync documentation of main branch

Author: actions-user

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

@@ -86728,7 +86728,11 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-If set to `true`, then this REST Client will not the default exception mapper which always throws an exception if HTTP response code >= 400. This property is not applicable to the RESTEasy Client.
+If set to `true`, then this REST Client will not the default exception mapper which always throws an exception if HTTP response code >= 400.
+
+This property is only taken into account if the REST Client returns `jakarta.ws.rs.core.Response` or `org.jboss.resteasy.reactive.RestResponse`
+
+This property is not applicable to the RESTEasy Client.
 
 
 ifdef::add-copy-button-to-env-var[]

_generated-doc/main/config/quarkus-rest-client-config.adoc

@@ -1803,7 +1803,11 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-If set to `true`, then this REST Client will not the default exception mapper which always throws an exception if HTTP response code >= 400. This property is not applicable to the RESTEasy Client.
+If set to `true`, then this REST Client will not the default exception mapper which always throws an exception if HTTP response code >= 400.
+
+This property is only taken into account if the REST Client returns `jakarta.ws.rs.core.Response` or `org.jboss.resteasy.reactive.RestResponse`
+
+This property is not applicable to the RESTEasy Client.
 
 
 ifdef::add-copy-button-to-env-var[]

_generated-doc/main/config/quarkus-rest-client-config_quarkus.rest-client.adoc

@@ -1803,7 +1803,11 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-If set to `true`, then this REST Client will not the default exception mapper which always throws an exception if HTTP response code >= 400. This property is not applicable to the RESTEasy Client.
+If set to `true`, then this REST Client will not the default exception mapper which always throws an exception if HTTP response code >= 400.
+
+This property is only taken into account if the REST Client returns `jakarta.ws.rs.core.Response` or `org.jboss.resteasy.reactive.RestResponse`
+
+This property is not applicable to the RESTEasy Client.
 
 
 ifdef::add-copy-button-to-env-var[]

_generated-doc/main/infra/quarkus-all-build-items.adoc

@@ -8767,6 +8767,17 @@ _No Javadoc found_
 
 
 
+a| https://github.com/quarkusio/quarkus/blob/main/extensions/security/spi/src/main/java/io/quarkus/security/spi/CurrentIdentityAssociationClassBuildItem.java[`io.quarkus.security.spi.CurrentIdentityAssociationClassBuildItem`, window="_blank"]
+[.description]
+--
+Allows Quarkus core extensions to provide a `io.quarkus.security.identity.CurrentIdentityAssociation` implementation. This bean is used to synchronize the association produced by Quarkus core extensions and can change if needed. Other extensions and users can simply define alternative `io.quarkus.security.identity.CurrentIdentityAssociation` CDI bean.
+-- a|`java.lang.Class<? extends CurrentIdentityAssociation> currentIdentityAssociationClass` 
+
+_No Javadoc found_
+
+
+
+
 a| https://github.com/quarkusio/quarkus/blob/main/extensions/security/spi/src/main/java/io/quarkus/security/spi/DefaultSecurityCheckBuildItem.java[`io.quarkus.security.spi.DefaultSecurityCheckBuildItem`, window="_blank"]
 [.description]
 --

_versions/main/guides/hibernate-orm.adoc

@@ -100,7 +100,7 @@ They will often map to Hibernate ORM configuration properties but could have dif
 
 Also, Quarkus will set many Hibernate ORM configuration settings automatically, and will often use more modern defaults.
 
-For a list of the items that you can set in `{config-file}`, see <<hibernate-configuration-properties,Hibernate ORM configuration properties>>.
+For a list of the items that you can set in `{config-file}`, see <<configuration-reference>>.
 
 An `EntityManagerFactory` will be created based on the Quarkus `datasource` configuration as long as the Hibernate ORM extension is listed among your project dependencies.
 
@@ -295,9 +295,7 @@ There are no required properties, as long as a default datasource is configured.
 When no property is set, Quarkus can typically infer everything it needs to set up Hibernate ORM
 and will have it use the default datasource.
 
-The configuration properties listed here allow you to override such defaults, and customize and tune various aspects.
-
-include::{generated-dir}/config/quarkus-hibernate-orm.adoc[opts=optional, leveloffset=+2]
+The configuration properties listed in <<configuration-reference>> allow you to override such defaults, and customize and tune various aspects.
 
 [NOTE]
 ====
@@ -314,20 +312,6 @@ quarkus.hibernate-orm.persistence-xml.ignore=true
 ----
 ====
 
-[TIP]
-====
-Want to start a PostgreSQL server on the side with Docker?
-
-[source,bash]
-----
-docker run --rm=true --name postgres-quarkus-hibernate -e POSTGRES_USER=hibernate \
-           -e POSTGRES_PASSWORD=hibernate -e POSTGRES_DB=hibernate_db \
-           -p 5432:5432 postgres:14.1
-----
-
-This will start a non-durable empty database: ideal for a quick experiment!
-====
-
 [[multiple-persistence-units]]
 === Multiple persistence units
 
@@ -961,7 +945,7 @@ quarkus.hibernate-orm."offline".dialect.mariadb.bytes-per-character=1
 quarkus.hibernate-orm."offline".dialect.mariadb.no-backslash-escapes=true
 ----
 
-Refer to the <<hibernate-configuration-properties,Hibernate ORM configuration properties>> section for more details on the available properties.
+Refer to the <<configuration-reference>> section for more details on the available properties.
 
 
 [[caching]]
@@ -1949,3 +1933,8 @@ to learn more about the `dataStore` attribute.
 Please refer to the corresponding https://hibernate.org/repositories/[Hibernate Data Repositories]
 and https://jakarta.ee/specifications/data/1.0/jakarta-data-1.0[Jakarta Data]
 guides to learn what else they have to offer.
+
+[[configuration-reference]]
+== Configuration Reference for Hibernate ORM
+
+include::{generated-dir}/config/quarkus-hibernate-orm.adoc[opts=optional, leveloffset=+2]

_versions/main/guides/hibernate-reactive.adoc

@@ -116,7 +116,7 @@ Blocking (non-reactive) and reactive configuration xref:orm-and-reactive-extensi
 
 WARNING: Configuring Hibernate Reactive using the standard `persistence.xml` configuration file is not supported.
 
-See section <<hr-configuration-properties,Hibernate Reactive configuration properties>> for the list of properties you can set in `{config-file}`.
+See section <<configuration-reference>> for the list of properties you can set in `{config-file}`.
 
 A `Mutiny.SessionFactory` will be created based on the Quarkus `datasource` configuration as long as the Hibernate Reactive extension is listed among your project dependencies.
 
@@ -193,24 +193,7 @@ and will have it use the default datasource.
 
 The configuration properties listed here allow you to override such defaults, and customize and tune various aspects.
 
-Hibernate Reactive uses the same properties you would use for Hibernate ORM. You will notice that some properties
-contain `jdbc` in the name but there is no JDBC in Hibernate Reactive, these are simply legacy property names.
-
-include::{generated-dir}/config/quarkus-hibernate-orm.adoc[opts=optional, leveloffset=+2]
-
-[TIP]
-====
-Want to start a PostgreSQL server on the side with Docker?
-
-[source,bash]
-----
-docker run --rm --name postgres-quarkus-hibernate -e POSTGRES_USER=quarkus_test \
-           -e POSTGRES_PASSWORD=quarkus_test -e POSTGRES_DB=quarkus_test \
-           -p 5432:5432 postgres:14.1
-----
-
-This will start a non-durable empty database: ideal for a quick experiment!
-====
+Hibernate Reactive uses the same properties you would use for Hibernate ORM: see <<configuration-reference>>.
 
 [[orm-and-reactive-extension-simultaneously]]
 === Hibernate ORM and Reactive extensions simultaneously
@@ -446,3 +429,16 @@ by providing active record style entities (and repositories) and focuses on maki
 To find out more on how the <<quarkus-hibernate-orm_quarkus-hibernate-orm-validation-mode,`quarkus.hibernate-orm.validation.mode` configuration property>>.
 influence your Hibernate Reactive application see the xref:hibernate-orm.adoc#validator_integration[corresponding Hibernate ORM guide],
 as these modes work the same in both cases.
+
+[[configuration-reference]]
+== Configuration Reference for Hibernate Reactive
+
+[TIP]
+====
+You will notice that some properties
+contain "jdbc" in their name: this is because Hibernate ORM refers to its "data access" layer as "JDBC" for historical reasons. Hibernate Reactive uses Vert.x Reactive SQL clients for its data access layer rather than JDBC.
+
+Regardless of their name, these properties still make sense for Hibernate Reactive.
+====
+
+include::{generated-dir}/config/quarkus-hibernate-orm.adoc[opts=optional, leveloffset=+2]

_versions/main/guides/rest-client.adoc

@@ -1334,7 +1334,7 @@ Alternatively, you can implement the `ResteasyReactiveClientRequestFilter` inter
 public class TestClientRequestFilter implements ResteasyReactiveClientRequestFilter {
 
     @Override
-    public void filter(ResteasyReactiveClientRequestFilter requestContext) {
+    public void filter(ResteasyReactiveClientRequestContext requestContext) {
         Providers providers = requestContext.getProviders();
         // ...
     }