On Aug 14, 2009, at 6:47 PM, Craig McClanahan wrote:
>> I don't think this violates anything specific to Guice's approach
>> to ensuring all things are bound at module initialization (e.g. so
>> one could output a dependency graph). It does however, make things
>> less explicit due to the integration of the meta provider. But i
>> would not expect most developers to create meta providers and
>> instead they would be created by the much smaller set of framework
>> developers to be reused. But, i suspect the probability of this
>> concept getting accepted by the Guice developers may well be close
>> to zero...
>>
> I suspect you might be right.
>
> I'm also going to play a little with GuiceyFruit and see if James
> got anywhere on this sort of thing. But I suspect he's not focused
> on integration with frameworks.
IIUC James's managed to get most (if not all of his patches in some
form or other accepted) thus GuiceyFruit no longer needs to maintain
its own patched version of Guice.
Constructor injection integration is still on the TODO list.
Paul.