Thanks for your mail. Basically the extension must load properly for Tamaya CDI to work. If you can provide some kind of sample project it would be perfect and I am happy to help.
J Anatole ajs6f <[email protected]> schrieb am Do., 23. Aug. 2018, 22:00: > Hi, Tamaya-folks! > > I'm tinkering with Tamaya (0.3-incubating) for a webapp I'm writing > (deployed as a WAR in a servlet container). I'm using JAX-RS (Jersey 2.27) > and CDI (Weld 3.0.5.Final) and I would love to use tamaya-cdi, but I'm > running into an odd problem. > > I'm not seeing TamayaCDIInjectionExtension properly initialized as a CDI > extension, but oddly, I _am_ seeing the TamayaCDIAccessor extension show up > and get initialized. So when my bean wirings are validated, injection > points with a @Config @Inject are failing because CDI doesn't know to go to > Tamaya for such injections. > > Has anyone seen anything like this? I can certainly put my current branch > up somewhere if that would be useful. My > javax.enterprise.inject.spi.Extension is as simple as: > > # Register Tamaya to perform injection > org.apache.tamaya.cdi.TamayaCDIAccessor > org.apache.tamaya.cdi.TamayaCDIInjectionExtension > > but only one of those guys seems to come to life! :grin: > > ajs6f > > > >
