You probably want to call:
binder.requireExplicitBindings() in your Guice Module to catch these kinds
of errors earlier than later.
There are other methods that might solve your needs (like
requireAtInjectOnConstructors), see:
I just ran into this today and think it might be a bug?
I have a ProviderFoo which kind of implies that it would be explicitly
setup in a binding.
But it looks like the default constructor was being called.
This was giving me an non-started ActiveMQ broker which wasn't working.
Doesn't
Show us the code - it's not clear what your problem is. Whose default
constructor is being called - Foo or the provider you wrote? Or did you
not write a provider?
-Tim
--
You received this message because you are subscribed to the Google Groups
google-guice group.
To unsubscribe from this
NICE ... that's probably just what I need!
On Monday, April 6, 2015 at 12:21:18 PM UTC-7, Nate Bauernfeind wrote:
You probably want to call:
binder.requireExplicitBindings() in your Guice Module to catch these kinds
of errors earlier than later.
There are other methods that might solve
