Comment by [email protected]:
a provider in the same package is reasonable - you can still use that
provider in any module in other packages
also, this is a recommendation because of the nastiness that can ensue with
tight coupling - if you also need to use that same exact class in a non-DI
environment, then by all means don't worry about making the constructor
non-public, by that merely means that in the non-DI environment you'll have
tight coupling => hence the recommendation as it assumes DI in the premise
of the argument
For more information:
http://code.google.com/p/google-guice/wiki/KeepConstructorsHidden
--
You received this message because you are subscribed to the Google Groups
"google-guice-dev" 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-dev?hl=en.
