There are several ways to do it.
You can simply introduce logic in you modules which allows to configure
the bindings at startup time.
This is the simplest way but if the logic gets complexer it will also be
hard to understand.
You can group bindings which belong together into modules and then
Thanks, that helped me ramp up on the guice ecosystem and configuration.
However - the fact that setDefault has different binding coercion semantics
to setBinding smells like a bug to me. Is there any reason that its current
behaviour is the correct one? If not I might file a bug report.
On
Awesome, we just migrated our application to onami-persist. I had a look at
the source code, it looks much better.
Thanks guys.
Le jeudi 22 janvier 2015 08:03:35 UTC+11, scl a écrit :
>
> Regarding persist-extension see:
> https://groups.google.com/d/topic/google-guice/Dp9nWdmDbUs/discussion