Barring the separate issue with the final modifier, you can achieve your aim of getting the logger injected with the classname defined for you by Guice.
You'll need to employ a custom injection to get it working (http://code.google.com/p/google-guice/wiki/CustomInjections). It is possible to still use the normal @Inject annotation with some additional checks using reflection to make the integration a little simpler. YMMV. Hope this helps. I did something similar previously for a contract where the company decided on writing their own logger (why?) and wanted it injected. On Wed, May 11, 2011 at 7:23 PM, Lucas Cavalcanti <[email protected]> wrote: > change the imports on the template to the respective Log4j (or your logging > library) code > > On Wed, May 11, 2011 at 2:12 PM, Jarrod Roberson <[email protected]> > wrote: >> >> because I don't want to use slf4j >> >> -- >> 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. > > -- > 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. > -- 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.
