Fred, granted its Friday, but this just cramped my frontal lobe.  If
you get a shot, could you elaborate on what scenario I might use
something like this in?  Thx and Happy Friday!

On Mar 12, 12:09 pm, Fred Faber <[email protected]> wrote:
> Incidentally, and as a general note to similar problems, if you need an
> ordering and you know you're binding all contributions from the same module
> then you can use a MapBinder with an incrementing key value, then use a
> Provider as such:
>
> bind(new TypeLiteral<List<TemplateFinder>>(){})
>   .toProvider(new Provider<List<TemplateFinder>(){
>
>         @Inject Map<Integer, TemplateFinder> templates;
>
>         �...@override
>          public List<TemplateFinder> get() {
>               // sort the keyset of templates
>               // iterate over the sorted keyset, and add templates.get(key)
> to the list
>           }
>
>
>
> }
> On Fri, Mar 12, 2010 at 11:55 AM, Fred Faber <[email protected]> wrote:
> > There are a number of ways to do this, but if you don't need ordering, then
> > can you use a Multibinder?
>
> >http://code.google.com/p/google-guice/wiki/Multibindings
>
> > You would simply inject ArtifactLocator with Set<TemplateFinder>, and add
> > each TemplateFinder to the Multibinder in your module.
>
> > -Fred
>
> > On Fri, Mar 12, 2010 at 11:00 AM, Ilya Sterin <[email protected]> wrote:
>
> >> I have a guice project with multiple guice modules when are then used
> >> to create an injector.  Nothing unusual.
>
> >> I have a chain of responsibility implementation where there is a
> >> object, which needs to accumulate all command objects to initialize.
>
> >> So there is a class Locator, which has a list of Finder instances.
> >> Some Finder instances have dependencies which I want wired by guice.
>
> >> I want to perform this type of initialization in the module (I would
> >> think this is the best place for it).  The problem is that doing the
> >> initialization yourself and then using toInstance() doesn't inject any
> >> of the Finder setter dependencies.  Here is an example...
>
> >> ArtifactLocator locator = new ArtifactLocator();
> >> locator.addFinder(new RaceTemplateFinder());
> >> locator.addFinder(new EventTemplateFinder());
> >> locator.addFinder(new ClasspathTemplateFinder());
>
> >> bind(ArtifactLocator.class).toInstance(locator);
>
> >> The issue here is that Race and Event template finders have a
> >> dependency I want wired by guice.  I know I can possibly bypass this
> >> with Providers, but it just seems rather ugly, to have to write a
> >> provider for every Finder we might implement.  Is there a better way
> >> of doing this, or am I missing something?
>
> >> Thanks.
>
> >> Ilya
>
> >> --
> >> You received this message because you are subscribed to the Google Groups
> >> "google-guice" group.
> >> To post to this group, send email to [email protected].
> >> To unsubscribe from this group, send email to
> >> [email protected]<google-guice%2bunsubscr...@google­groups.com>
> >> .
> >> For more options, visit this group at
> >>http://groups.google.com/group/google-guice?hl=en.- Hide quoted text -
>
> - Show quoted text -

-- 
You received this message because you are subscribed to the Google Groups 
"google-guice" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-guice?hl=en.

Reply via email to