Migration Guide 3.16

Table of Contents

• Big Reactive Rename compatibility layer gone
• WebSockets Next

Note	We highly recommend the use of quarkus update to update to a new version of Quarkus. Items marked below with ⚙️ ✅ are automatically handled by quarkus update.

Big Reactive Rename compatibility layer gone

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.

WebSockets Next

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.