If the purpose of the final configuration would be to do more configuration, it'd be a nightmare to manage. Who gets to have the "last" say in the final configuration?
If you want to process your modules and do stuff to them, I suggest writing something like: createInjector(new DoStuffFromProcessingModule(new MyModule()), new MyModule()); ... where "MyModule" is your real Module, and DoStuffFromProcessingModule uses the Elements SPI (and the Multibinders SPI<https://code.google.com/p/google-guice/wiki/Multibindings#Inspecting_Multibindings_or_MapBindings__(new_in_Guice_3.0)>specifically, if you're interested in Multibindings) to do stuff you're interested in. sam On Fri, Jun 14, 2013 at 12:38 PM, <[email protected]> wrote: > It would be useful to have some kind of hook which would be called once > all modules are configured and that would allow some final configuration. > > But I guess there is a better way to implement what I'm trying to do. I'll > think about it... > > Thank you for the help! > > -- > You received this message because you are subscribed to the Google Groups > "google-guice" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/google-guice. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "google-guice" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-guice. For more options, visit https://groups.google.com/groups/opt_out.
