Hi The non proxied impl just works in request scoped case when used in a single request duration (more generally when lookup is not used outside of looked up instance lifetime) so quite a particular case not framework friendly. I'm clearly to not break CDI and EL integration and rather clarify - not a breaking change - the spec to behave properly and not limit EL to JSF usage.
Guess rational was to enable custom injections but dependent scope is a trivial equivalent solution and cdi integration is everywhere now so not a valid reason IMHO. Le ven. 30 avr. 2021 à 13:07, Xavier Dury <[email protected]> a écrit : > Hi, > > I noticed a difference in behavior between OWB and Weld and wanted to > start a discussion to know which one is right. > > It seems that a normal-scoped bean resolved in an EL expression will be > the proxied bean for OWB and the non-proxied bean ("contextual instance") > in Weld. > > When I asked why the bean returned by Weld was not a proxy, I was directed > to that point of the spec > https://jakarta.ee/specifications/cdi/3.0/jakarta-cdi-spec-3.0.html#el > which says that the ELResolver must return a contextual instance (so not a > proxy). > > When I tested the same code with OWB, I got a proxy... so both > implementations differ in that matter. > > Personally, I prefer the way OWB does it and I don't see where the > motivation to return a contextual instance stems from... > > Regards, > Xavier
