[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [e4-dev] ExtendedObjectSupplier and access to the context
|
Thanks Paul for this validation, maybe this could be added to the Javadoc, it is always nice to have the intention of an API documented.
------------
The ExtendedObjectSuppliers are expected to reach outside the context to find their source/supply.
-----------
Putting additional logic into the one PrimaryObjectSupplier feel wrong to me, this would create more an more complexity on the core engine which should remain lean IMHO. I think in the future an extension of the PrimaryObjectSupplier would be nice which allows to change the search strategy. Something like IContextFunction but not for types but for additional customer annotations.
Best regards, Lars
2013/4/2 Paul Webster
<pwebster@xxxxxxxxxxxxxxxxxxx>
On Tue, Apr 2, 2013 at 7:09 AM, Lars Vogel
<lars.vogel@xxxxxxxxx> wrote:
I think it would be useful if we could use an ExtendedObjectSupplier for this, so that the core of the DI framework stays simple and lean. Unfortunately AFAIK ExtendedObjectSupplier does not provide access to the current context.
Is this by design or would it be possible to pass the current context to the ExtendedObjectSupplier?
That's fundamentally by design. The ExtendedObjectSuppliers are expected to reach externally to find their source/supply.
@Adapt is not so much another supplier but a modifier on the PrimaryObjectSupplier, in much the way that Optional is, no?
PW
--
Paul Webster
Hi floor. Make me a sammich! - GIR
_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/e4-dev
