Awesome, thank you very much. I think it would be enough to use the sample provided by pax-cdi [1].
What I am wondering is, that the web-implementations in pax-cdi (currently Jetty and Undertow) use different approaches: for example, pax-cdi-web-undertow-weld provides a faces-config [2] while the others dont. That's why I am currently trying to get my examples to run on Undertow rather than Jetty, hoping that this might solve the issue. If you need another example/integration-test for pax-web I can create one. regards Marc [1] https://github.com/ops4j/org.ops4j.pax.cdi/tree/master/pax-cdi-samples/pax-cdi-sample4-jsf [2] https://github.com/ops4j/org.ops4j.pax.cdi/blob/master/pax-cdi-undertow-weld/src/main/resources/META-INF/faces-config.xml Am Mittwoch, 12. Oktober 2016 14:48:32 UTC+2 schrieb Guillaume Nodet: > > I'm willing to investigate this issue. > Can someone come up with a complete list of features / bundles to install > to reproduce the problem ? > > Guillaume > > Le mardi 17 mai 2016 13:21:42 UTC+2, Marc Schlegel a écrit : >> >> Is there anything we can do about PAXCDI-210 >> <https://ops4j1.jira.com/projects/PAXCDI/issues/PAXCDI-210>? >> >> I came accross this issue today as well while updating a JSF-example >> (using Pax-Web) to use CDI-Beans instead of the old ManagedBeans. The >> JSF-expression cannot resolve the Cdi-bean. >> >> It seems that Pax-Web doesnt know that Pax-Cdi is managing the beans. >> >> regards >> Marc >> > -- -- ------------------ OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
