Martin Kouba

I have to admit that I'm a bit confused. In any case, the WARN messages in the original `Issue_upgrading_from_261_to_280_results_in_Failed_to_star_quarkus.txt` and https://github.com/quarkusio/quarkus/issues/25236#issuecomment-1286530885 are not the cause - there's always a follow-up...

@Ladicek @manovotn What's the current compliance status?

Well, the fact that the `AfterDeploymentValidation` event must be fired **before** the contexts are created does not imply that the contexts must be created **after** all `AfterDeploymentValidation` observers are notified....

The problem with a `java.lang.reflect.Type` subtype parameter is that it's not type-safe. I think there was a similar discussion for `javax.enterprise.inject.Instance` in JIRA and the result was a non-portable method...

> Enable TypeLiteral to get a Type `javax.enterprise.util.TypeLiteral.getType()`?

+1 for both, i.e. `@Alternative` producer methods and fields.

> Currently, a producer is enabled if the declaring bean is enabled. We probably want to keep that? That is, if there's a producer that declares a `@Priority`, but the...

Hi Markus, I'm not sure I fully understand but keep in mind that if you fire an event synchronously, e.g. via `Event.fire()` then the method invocation completes once all sync...

So CDI events are not designed for point-to-point messaging. It's more a publish/subscribe style of messaging where observers represent the _subscribe_ part and `Event#fire()` represents the _publish_ part. For sync...

There is one more difference: `@Observes @Initialized(ApplicationScoped.class)` is not saying anything about the application itself. It's fired when the application context is initialized. Whereas `@Observes StartupEvent` and `@io.quarkus.runtime.Startup` (since Quarkus...