Extract from todays (23 july 2009) discussion on
"firstname.lastname@example.org" with title "IoCComponentProviderFactory and
injection of Jersey-based artifacts"
Need a solution for Jersey to ask the IoCComponentProviderFactory if it can
resolve types. Thus an implementation of IoCComponentProviderFactory could also
// Resolve scope + type + annotations to an instance
When Jersey injects for constructor, field and methods, if it cannot resolve an
injection point from its own registered injection stuff it can defer to the
InjectableResolver implemented by the IoCComponentProviderFactory
implementation. This has the advantage that as well as constructors, resource
methods, sub-resource methods and sub-resource locators can also have stuff
injected as supplied by the IoCComponentProviderFactory.
For the solution where the IoC framework manages life-cycle i think we need the
IoCComponentProviderFactory implementation to get an instance of
InjectableResolver from Jersey. Thus for constructor the factory can use the