Sync web site with Quarkus documentation

Author: quarkusbot

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

@@ -4426,7 +4426,7 @@ a| https://github.com/quarkusio/quarkus/blob/main/extensions/devui/deployment-sp
 [.description]
 --
 This hold all files in the user's project root
--- a|`java.util.List<WorkspaceItem> workspaceItems` 
+-- a|`io.quarkus.devui.spi.workspace.WorkspaceItems workspaceItems` 
 
 _No Javadoc found_
 

_guides/_attributes.adoc

@@ -1,7 +1,7 @@
 // Common attributes.
 // --> No blank lines (it ends the document header)
 :project-name: Quarkus
-:quarkus-version: 3.28.3
+:quarkus-version: 3.28.4
 :quarkus-platform-groupid: io.quarkus.platform
 // .
 :maven-version: 3.9.11

_guides/extension-writing-dev-service.adoc

@@ -118,7 +118,7 @@ For example,
 
 [source,java]
 ----
-@BuildStep(onlyIfNot = IsNormal.class, onlyIf = GlobalDevServicesConfig.Enabled.class)
+@BuildStep(onlyIfNot = IsNormal.class, onlyIf = DevServicesConfig.Enabled.class)
 public DevServicesResultBuildItem createContainer(MyConfig config) {}
 ----
 

_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
 
@@ -908,7 +892,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]]
@@ -1895,3 +1879,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]

_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
@@ -428,3 +411,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]

_guides/logging.adoc

@@ -497,7 +497,7 @@ Log file rotation ensures efficient log management by preserving a specified num
 +
 [source, properties]
 ----
-quarkus.log.file.enable=true
+quarkus.log.file.enabled=true
 quarkus.log.file.path=application.log
 quarkus.log.file.format=%d{yyyy-MM-dd HH:mm:ss} %-5p [%c] (%t) %s%e%n
 ----
@@ -506,7 +506,7 @@ quarkus.log.file.format=%d{yyyy-MM-dd HH:mm:ss} %-5p [%c] (%t) %s%e%n
 +
 [source, properties]
 ----
-quarkus.log.handler.file.my-file-handler.enable=true
+quarkus.log.handler.file.my-file-handler.enabled=true
 quarkus.log.handler.file.my-file-handler.path=application.log
 quarkus.log.handler.file.my-file-handler.format=%d{yyyy-MM-dd HH:mm:ss} [com.example] %s%e%n
 
@@ -529,7 +529,7 @@ When enabled, it sends all log events to a syslog server, typically the local sy
 +
 [source, properties]
 ----
-quarkus.log.syslog.enable=true
+quarkus.log.syslog.enabled=true
 quarkus.log.syslog.app-name=my-application
 quarkus.log.syslog.format=%d{yyyy-MM-dd HH:mm:ss} %-5p [%c] (%t) %s%e%n
 ----
@@ -538,7 +538,7 @@ quarkus.log.syslog.format=%d{yyyy-MM-dd HH:mm:ss} %-5p [%c] (%t) %s%e%n
 +
 [source, properties]
 ----
-quarkus.log.handler.syslog.my-syslog-handler.enable=true
+quarkus.log.handler.syslog.my-syslog-handler.enabled=true
 quarkus.log.handler.syslog.my-syslog-handler.app-name=my-application
 quarkus.log.handler.syslog.my-syslog-handler.format=%d{yyyy-MM-dd HH:mm:ss} [com.example] %s%e%n
 
@@ -559,7 +559,7 @@ When enabled, it sends all log events to a socket, such as a Logstash server.
 +
 [source, properties]
 ----
-quarkus.log.socket.enable=true
+quarkus.log.socket.enabled=true
 quarkus.log.socket.endpoint=localhost:4560
 ----
 
@@ -641,7 +641,7 @@ For example, `-Dquarkus.log.category.\"io.quarkus\".level=DEBUG`.
 .File TRACE logging configuration
 [source, properties]
 ----
-quarkus.log.file.enable=true
+quarkus.log.file.enabled=true
 # Send output to a trace.log file under the /tmp directory
 quarkus.log.file.path=/tmp/trace.log
 quarkus.log.file.level=TRACE
@@ -664,7 +664,7 @@ quarkus.log.console.format=%d{HH:mm:ss} %-5p [%c{2.}] (%t) %s%e%n
 # Configure a named handler that logs to console
 quarkus.log.handler.console."STRUCTURED_LOGGING".format=%e%n
 # Configure a named handler that logs to file
-quarkus.log.handler.file."STRUCTURED_LOGGING_FILE".enable=true
+quarkus.log.handler.file."STRUCTURED_LOGGING_FILE".enabled=true
 quarkus.log.handler.file."STRUCTURED_LOGGING_FILE".format=%e%n
 # Configure the category and link the two named handlers to it
 quarkus.log.category."io.quarkus.category".level=INFO
@@ -676,7 +676,7 @@ quarkus.log.category."io.quarkus.category".handlers=STRUCTURED_LOGGING,STRUCTURE
 [source, properties]
 ----
 # configure a named file handler that sends the output to 'quarkus.log'
-quarkus.log.handler.file.CONSOLE_MIRROR.enable=true
+quarkus.log.handler.file.CONSOLE_MIRROR.enabled=true
 quarkus.log.handler.file.CONSOLE_MIRROR.path=quarkus.log
 # attach the handler to the root logger
 quarkus.log.handlers=CONSOLE_MIRROR

_guides/rest-client.adoc

@@ -157,7 +157,7 @@ import jakarta.ws.rs.QueryParam;
 import jakarta.ws.rs.core.MultivaluedMap;
 import java.util.Map;
 import java.util.Set;
-import java util.Optional;
+import java.util.Optional;
 
 @Path("/extensions")
 @RegisterRestClient(configKey = "extensions-api")
@@ -466,7 +466,7 @@ The name of the property needs to follow a certain convention which is best disp
 [source,properties]
 ----
 # Your configuration properties
-quarkus.rest-client."org.acme.rest.client.ExtensionsService".url=https://stage.code.quarkus.io/api # // <1>
+quarkus.rest-client."org.acme.rest.client.ExtensionsService".url=https://stage.code.quarkus.io/api // <1>
 ----
 
 <1> Having this configuration means that all requests performed using `org.acme.rest.client.ExtensionsService` will use `https://stage.code.quarkus.io/api` as the base URL.
@@ -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();
         // ...
     }

_guides/security-oidc-expanded-configuration.adoc

@@ -1312,6 +1312,10 @@ According to the https://datatracker.ietf.org/doc/rfc9728/[OAuth2 Protected Reso
 
 If it is configured as a relative path then it is added to the current request URL's host and port to build a resource identifier URL. If it is not configured at all then, unless it is a default tenant id, the tenand id is added to the current request URL's host and port to build a resource identifier URL.
 
+By default, when no `quarkus.oidc.resource-metadata.resource` is configured, a protected resource metadata route is available at a `/.well-known/oauth-protected-resource` relative address.
+
+Setting `quarkus.oidc.resource-metadata.resource` to a relative value impacts the protected resource metadata route's address. For example, setting `quarkus.oidc.resource-metadata.resource=resource` for a default OIDC tenant makes its protected resource metadata route available at `/.well-known/oauth-protected-resource/resource`.
+
 The resource identifier URL scheme is set to `HTTPS` by default. You can enable an `HTTP` URL scheme with `quarkus.oidc.resource-metadata.force-https-scheme=false`, it can be particularly useful in simple demos and tests.
 
 `quarkus.oidc.resource-metadata.authorization-server` allows to customize an authorization server URL that will be included in the resource metadata. The `quarkus.oidc.auth-server-url` URL is included by default, however, for some cases where an OIDC proxy interposes over the actual OIDC provider, returning the OIDC proxy's URL is required instead.