Ladislav Thon

Just wanted to write down a few notes of my own. The duplicated context is easy to access concurrently in pure Vert.x (a simple [example](https://github.com/Ladicek/vertx-tinies/blob/main/duplctx/src/main/java/cz/ladicek/vertx/tiny/duplctx/MainVerticle.java)). It is also heavily used...

This not a valid TCK challenge. I'm moving the issue to the `cdi` repository for further discussion.

This issue is extremely vague. It might be just me, but I can't understand what the objection here really is. For the record, it is impossible to declare annotations in...

Please stop the passive-aggressive tone. CDI decorators can actually do what you want with zero class explosion, looking roughly like this: ```java interface Notifier { void notify(Message m); } @ApplicationScoped...

Yeah, I generally agree the best solution for composing notifications to external systems is a dedicated service (not necessarily a dedicated program, but that might be an option too). CDI...

I believe this also applies to `ProcessObserverMethod.veto()`, though there's no such mess as with `ProcessBeanAttributes`.

The `producer.send()` operation is already called on a worker thread (`ctx.executeBlocking()`), so this helps nothing AFAICT.

Draft for now, because of the 3.2.0 target. Other than that, this should be ready.

It should be fairly simple to add a pair of method like `RedisOptions.setStaticMaster()` and `RedisOptions.setStaticReplicas()`. If they are called, the provided values would be used instead of automatic discovery from...

I have an implementation (in this branch https://github.com/Ladicek/vertx-redis-client/commits/static-topology/) that allows configuring topology statically for the replication client. In the end, I decided to just add a flag whether current configuration...