Matej Novotny

What Martin says is that CDI functionality won't cut it for your scenario. If you wanted CDI to handle it, you'd have to turn it around - instead of thread...

> Is that an official way of achieving at-startup or it just so happens to work? Yes, that's official. If you add such an obsever into a bean, an instance...

@aguibert the reason Quarkus has this is because `ApplicationScoped` in JVM mode is started before you get to runtime (in `STATIC_INIT`). This causes differences in behaviour when running in JVM...

The line between what events are container lifecycle ones and which are standard ones is (IMO) pretty well defined, I would try and avoid blurring it, so also -1. Besides,...

> The purpose of the scope is, that data is associated with a session without using the HttpSession as storage. So, would the scope still activate/deactivate based on session creation/timeout?...

> It solves the issue, by simply not replicating these beans. Ok, now I see what you mean. > Yeah, kind of. The storage would not be a "simple map"...

@codylerum thanks for creating the issue and restarting the discussion. I did re-read the issue and all other links but I am not JTA expert (so apply a pinch of...

> Its also possible to process all transaction observers from a transaction scoped queue within a single transaction synchronization that is always registered with an active transaction. I am not...

@tomjenkinson not sure I follow - how would that affect CDI spec, could you expand on it? Does that mean we would *always* register that synchronization or just use it...

@tomjenkinson Yea, so currently you can bind an observer to phases [listed as enum here](https://github.com/eclipse-ee4j/cdi/blob/master/api/src/main/java/jakarta/enterprise/event/TransactionPhase.java). Most important parts are `BEFORE_COMPLETION` and `AFTER_COMPLETION`, the rest is easily done with the former...