Arjan Tijms

The fix looks fine (so approved), but as Mojarra 2.3 has moved to Eclipse, I'm not sure I should fix the merge here. I'm not even sure why this repo...

Which Mojarra version are you using? Do you mean Mojarra 2.3.0 with JSF 2.3.0?

You might want to try the current 2.3.3 version and see how that works. In general, this relatively straightforward injection *should* really work as there are tests for this. Your...

I’ve given this some thought and there might be another possible reason. The problem is that it’s not clearly defined which bean archive(s) CDI.current() applies to. In some servers, CDI.current()...

Ok, I just checked and CdiUtils#createConverter uses the JNDI bean manager, so this can’t really be the issue here.

>The CDI.current() is the workaround which works. I'm using this but it is kinda ugly =) It is the @Inject which is not working. I know, but you are calling...

I should indeed still write something about that, it's on my TODO but didn't find the time yet. I've no idea yet why in EAP 7 you're seeing those issues....

The injection SPI itself did not change between 2.2 and 2.3 really. In 2.4 there’s a change again, but as far as a remember not in 2.3. But more importantly,...

For the JSF application, `@FacesConfig` has to be present once. You don't have to actually annotate the CDI bean that you want to inject with it, it can be present...

Thanks for the report. This is another case of where Java EE code looks directly at classes and forgets that in CDI things are a bit more dynamic. Various interceptors...