> I think Ceki's comment at the end is quite pertinent. But in the end, my > reaction to that article is pretty much, "I'd love to see a real world > example of someone doing that". I doubt you'll find many.
Some people argue that logging itself can be evil because logging too much almost hides information. I will not go there but I guess it heavily depends how you use logging in the first place. I was involved in a project where debug logging was activated through an aspect. Everything else was essentially error logging. For the libraries we used a very simple facade that came with the project. So no dependency at all. The actual main project implemented the facade and forwarded to the appropriate logging system. Very simple. Using the aspect we could easily pick the right class/package and the method calls in there. Of course this cannot give you back a debug log in retrospect. But I was surprised how well this worked. Anyway ...enough logging chit-chat :) cheers -- Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
