search

google-code-export / google-guice

Automatically exported from code.google.com/p/google-guice
Apache License 2.0
2 stars 1 forks source link

Log binding resolving #140

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Sometimes you're using implicit bindings without knowing it. It would be 
useful to have a log of what Guice is doing behind the scenes, especially 
with implicit bindings.

This is a follow-up to the discussion at 
http://groups.google.com/group/google-
guice/browse_frm/thread/4d6a44ece59cc3cc

Format to be discussed, but I guess all binding info (binding itself, and 
transitive resolving) and possibly the line number if there's an explicit 
binding for the Key being processed.

Original issue reported on code.google.com by robbie.v...@gmail.com on 9 Aug 2007 at 6:33

GoogleCodeExporter commented 9 years ago

Original comment by limpbizkit on 1 Jun 2008 at 7:35

GoogleCodeExporter commented 9 years ago

Original comment by sberlin on 22 Feb 2011 at 1:53

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Not sure how to handle this sort of thing yet - on one hand, we might want to 
enable stronger logging, but only if we can make sure we're not penalizing 
performance.  This almost feels like it's not looking for logging as much as a 
facility to query the bindings at run-time and get information out of them.  
This is possible with the SPI, and may be a nice extension.

Original comment by christia...@gmail.com on 4 Jun 2012 at 6:02

GoogleCodeExporter commented 9 years ago 
While we might want to add some more articulated logging (Want to wait and look 
at performance-neutral loggers), you can do this with the SPI (provision 
listener), so I'm going to close this.

Original comment by cgruber@google.com on 18 Nov 2013 at 7:58