Hello, User guide advertises built-in bindings for java.util.logging.Logger (http://code.google.com/docreader/#p=google-guice&s=google- guice&t=BuiltInBindings), and I like the idea a lot - get rid of boilerplate, can actually test that loggers log etc.
My project uses a lot of @Provides method and sometime we switch between @Inject and @Provides If I switch to built-in logger binding with @Inject for constuctor, does it prevent me from switching to @Provides, as @Provides method won't know the name of the class being logged, and would give me anonymous logger (getName() => null)? Is there a known solution/workaround for java.util.logging.Logger in @Provides methods? Sincerely, Alexander -- You received this message because you are subscribed to the Google Groups "google-guice" 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?hl=en.
