Updates:
Status: WontFix
Comment #5 on issue 269 by sberlin: Move Logger binding out to
LoggerModule, so users can bind their own Loggers
http://code.google.com/p/google-guice/issues/detail?id=269
Guice special-cases java.util.logging.Logger because it can and because
it's part of the JDK. Adding a bindLogger call could be abused, and is
more or less an unnecessary addition to the API because the same thing can
be done in other ways with the existing API.
Some potential solutions without changing the API:
* Use an @InjectLogger approach
(http://code.google.com/p/google-guice/wiki/CustomInjections)
* Use something like Slf4jModule from Sitebricks
(http://code.google.com/p/google-sitebricks/source/browse/trunk/slf4j/src/main/java/com/google/inject/slf4j/Slf4jModule.java)
* Inject your LogFactory instead of a Logger, if really want constructor
injection.
* Don't inject your loggers.
--
You received this message because you are subscribed to the Google Groups
"google-guice-dev" group.
To post to this group, send email to google-guice-dev@googlegroups.com.
To unsubscribe from this group, send email to
google-guice-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-guice-dev?hl=en.
