-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Migration Guide 3.16
|
Note
|
We highly recommend the use of Items marked below with ⚙️ ✅ are automatically handled by |
In Quarkus 3.9, we renamed a lot of extensions and configuration properties when we rebranded RESTEasy Reactive to Quarkus REST and the Reactive Messaging extensions to Quarkus Messaging.
We introduced relocations for the artifacts and also fallbacks for the configuration properties.
In Quarkus 3.16, we dropped the relocations and the fallbacks for the configuration properties so you need to use the new artifacts and the new configuration properties.
See the Quarkus 3.9 migration guide for more context.
When an error occurs but no error handler can handle the failure, Quarkus uses the strategy specified by the quarkus.websockets-next.server.unhandled-failure-strategy configuration property. The default values changed. For server endpoints, the error message is logged and the connection is closed. For client endpoints, the error message is logged. Previously, for both server and client endpoints the connection was closed silently by default.
If HTTP compression is enabled the quarkus.http.compress-media-types configuration property defines the list of media types compressed.
The default value of this config property has changed.
The newly compressed media types include application/json and application/xhtml+xml.
The configuration properties for @Fallback.fallbackMethod() and @BeforeRetry.methodName() are now resolved at build time and so cannot be changed at runtime.
Specifically, the following configuration properties are affected:
-
<class name>/<method name>/Fallback/fallbackMethod -
<class name>/Fallback/fallbackMethod -
Fallback/fallbackMethod -
<class name>/<method name>/BeforeRetry/methodName -
<class name>/BeforeRetry/methodName -
BeforeRetry/methodName
This is to allow proper reflection configuration and native image compilation.
Configuration quarkus.datasource.jdbc.tracing was marked as deprecated for removal. This was a left over from the old, also deprecated OpenTracing based JDBC tracing.
Nowadays OpenTelementry, with this property should be used instead:
quarkus.datasource.jdbc.telemetry=true