Re: CDI-Bean in myfaces2.2 is not resolved

e > Internet: https://www.safir-wid.de > > safir Wirtschaftsinformationsdienst GmbH > Sitz der Gesellschaft: Möllendorffstr.49, 10367 Berlin > Geschäftsführer: Thilo Kind > Registergericht: Amtsgericht Berlin Charlottenburg, HRB 66681 > USt-ID: DE 193584747 > > > > ----

AW: CDI-Bean in myfaces2.2 is not resolved

, 10367 Berlin Geschäftsführer: Thilo Kind Registergericht: Amtsgericht Berlin Charlottenburg, HRB 66681 USt-ID: DE 193584747 -Ursprüngliche Nachricht- Von: Thomas Andraschko Gesendet: Mittwoch, 28. August 2019 16:03 An: MyFaces Discussion Betreff: Re: CDI-Bean in myfaces2.2 is not resolved

Re: CDI-Bean in myfaces2.2 is not resolved

Hi, in generell it's up to the container or the CDI impl, to add CDI support to JSF =< 2.2 via a ELResolver. In JSF 2.3 the direct support of the BeanManager#getELResolver was added (see MyFaces' 2.3 ResolverBuilderForFaces). In OpenWebBeans we did it within a wrapped JSF Application-Object: http

CDI-Bean in myfaces2.2 is not resolved

Hallo, In a small example Project we want to test the CDI-definition of managed Beans. We want to use myfaces2.2.8 and deploy to WildFly13. If we use the jsf version that is shipped with WildFly (mojarra2.2) the project works. If we use myfaces the request-scoped bean is not resolved an the proj