I browsed the source to find out why all my tests failed. The
BinderImpl(line 87ff) defines a LOGGER_FACTORY which always caused a
configuration error. The current behaviour is nice for single threaded
applications or ones that run inside of a container which reroutes the
logs anyway.

For multi threaded applications this is useless. With the current text
formatter, which doesn't log the thread id, you get a real mess from
dozens of threads all using the same class. If you register a
different formatter you still have a synchronisation issue of all the
threads that want to log to a single log (file).

How to replace the default behaviour?


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to