Hi all,
It appears to me from trying and looking at the source that the Jersey CDI Integration (via CDIComponentProviderFactory) will not automatically discover Root Resources (That is CDI Beans with a @Path on Class level) like the SPring Integration does. Is that right?
So if I manual add this resource to jersey (via an Custom Application or settings the packages to be scanned) what will the lifecycle of those Resource be like? Are they instantiated by Jersey or cdi?
By the way I'm happy to see the patch for Jersey-883 is now in the trunk. Caused me some trouble to find out this was the problem when using tomcat :-).
Regards,
Martin