Ladislav Thon

> Just a minor point of clarification - the extensions API is still mostly geared towards plug-in developers instead of business application developers, correct? That is my understanding, yes. Application...

Correct observation. `CDI.current()`, or `BeanContainer.createInstance()` for what it's worth, basically gives you an `Instance` which was not obtained by injection. Looking up an `InjectionPoint` from that, or a `@Dependent` bean...

I took the liberty of creating a _CDI 5.0_ milestone and assigning this issue to it. This is something that should be specified IMHO. Of course, my preference would be...

That's weird. When I log into the Red Hat JIRA, I can see CDITCK-416 just fine. I even get a warning that _This is a public project._ :shrug:

Maybe it isn't accessible to non-Red Hat people because the project is also archived...?

If you have hundreds of calls to `CDI.current()` in your code, you're likely doing something wrong (and performance likely suffers as well). I'd generally assume that you can `@Inject Instance`...

> I am accessing stateless service bean methods (running direct database queries) from entity beans. In the entity beans the following does not work: > > `@Inject ServiceBeanX serviceBeanX; `...

I'm no EL expert, but it seems to me that the EL specification actually allows this. The relevant evaluation mechanisms all have multiple options how something can be evaluated, and...

> EL + CDI -> does not work together reliably on a spec standpoint But that's just wrong. The CDI specification demands that CDI implementations provide an `ELResolver` that follows...

I don't think we support `Flow` anywhere, and there's a simple extension function for `Flow` to convert to `Multi` (see https://smallrye.io/smallrye-mutiny/latest/guides/kotlin/). This is available out of the box when you...