Use ExtendedObjectSupplier for pure @Inject annotations? [message #901496] |
Mon, 13 August 2012 07:27 |
|
Hi,
AFAIK, I can register my ExtendedObjectSupplier for my own annotations. Field, methods and the like need then to be annotated with both, @Inject and @MyAnnotation.
Is there a way to register an ExtendedObjectSupplier for pure @Inject annotations too? I'd like to seamlessly integrate my Guice injector into Eclipse DI - if possible.
Thanks
|
|
|
|
|
Re: Use ExtendedObjectSupplier for pure @Inject annotations? [message #901562 is a reply to message #901561] |
Mon, 13 August 2012 12:20 |
|
FWIW, I'm looking for ways how to migrate from Guice to e4 to make use of the dynamics of, for instance, @Preferences and the like.
Unfortunately, it seems to be "not as easy as I hoped" We have complex object data structures we assemble with Guice. For instantiating object graphs in e4 we use our own ExtensionFactory. It would be nice if registering an "elsewhere created" object with the e4 DI container would be possible. Then I may be able to get updates from the e4 DI container (for preferences updates for instance) but may continue assembling my objects using Guice.
Regarding the (implicit) question why I need two frameworks:
Converting Guice Modules to some kind of e4 configuration would be ultimate goal as soon as e4 supports generics properly and maybe offers a nice DI configuration interface. I don't have to rely on Guice in Eclipse 4.
Thanks for the comments
Marcel
|
|
|
Powered by
FUDForum. Page generated in 0.03737 seconds