Hi Morten,
Attached is a basic example of using Weld on SE with Jersey and Grizzly.
I think you were perhaps running into issues with dependences. Note
that JCDIComponentProviderFactory is not currently not part of the
public API. It has a dependency on the java EE annotations API. If we
want to make JCDIComponentProviderFactory public we can split the
class up to be CDI and CDI+EE dependent.
What the example does not support @RequestScoped. To do that requires
some additional declaration in Grizzly to declare a weld-based context
so it can manage the request-scoped classes when a request starts and
finishes.
I am assuming for the Grizzly Web-based support this should be
relatively straight forward e.g. a servlet context listener
declaration. However, for the low-level Grizzly support this will
require some specific Grizzly/Weld integration.
Paul.