[Snyk] Security upgrade io.vertx:vertx-core from 3.8.5 to 4.5.34 - #358

The upgrade from Vert.x 3.x to 4.x is a major version change with significant breaking changes that require code modifications and careful planning.

Key Breaking Changes:

• Asynchronous Operations: Vert.x 4 introduces a hybrid model using Future<T> for asynchronous operations alongside the traditional callback model. While callbacks are still supported to ease migration, many APIs now return Futures, and code will need to be adapted. For example, Future<T> now directly extends Handler<AsyncResult<T>>, and the completer() method has been removed.

• API Removals and Deprecations: APIs that were deprecated in 3.x have been removed in 4.x. For instance, the send method on the EventBus, deprecated in 3.x, is now removed and replaced by request.

• Stream and Messaging Changes: Several stream APIs are no longer fluent (i.e., they don't return this). WriteStream<T>.write() and WriteStream<T>.end() now return void or Future<Void>, which is a breaking change for chained calls. Additionally, MessageProducer no longer extends WriteStream.

• JSON Handling: The dependency on the Jackson Databind library is now optional. If your application performs object mapping from JSON, you must explicitly add the jackson-databind dependency. Methods in the Json class that exposed Jackson types have been removed and moved to DatabindCodec and JacksonCodec.

• Configuration: The ConfigRetriever.getConfigAsFuture() method has been removed and replaced with retriever.getConfig().

• Authentication/Authorization: The Shiro auth module has been deprecated in favor of new modules like vertx-auth-properties and vertx-auth-ldap.

Recommendation:
This is a high-risk migration that requires significant developer effort. Before upgrading, developers must thoroughly review the official Vert.x 3 to 4 migration guide. A dedicated branch and extensive testing will be necessary to handle the API changes, update dependencies, and adapt asynchronous programming patterns.

Source: Vert.x 3 to 4 Migration Guide

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}