On Wed, Apr 22, 2009 at 2:57 AM, Ralph Goers <ralph.go...@dslextreme.com> wrote:
> I'm not sure what you mean by "SLF4J bindings will start to be part of any
> major or minor component" and I think I've seen you make that comment
> before. Can you provide an example of how you think that will occur?
Easy. Suggest that you deliver a webapp (Pluto? :-), which contains a
SLF4J binding. Furthermore, suggest that there is another binding in
the web containers class path. Which one wins, aka is used? The answer
is: It depends on the classpath. If WEB-INF/lib takes precedence, then
the webapps binding is used. Otherwise, the containers binding will
win. Examples for both cases can be constructed.
In both cases, you'll encounter situations where logging won't work as
expected. Obviously, both container and webapp will likely contain
configurations for their respective logging system, aka binding. But,
if the other binding is used, then the respective logging
configuration will be ignored.
Again, I admit that such issues are possibly less likely, given
SFL4J's simplicity in that aspect. But it is a fairy tale, that such
things won't occur.
Jochen
--
I have always wished for my computer to be as easy to use as my
telephone; my wish has come true because I can no longer figure out
how to use my telephone.
-- (Bjarne Stroustrup,
http://www.research.att.com/~bs/bs_faq.html#really-say-that
My guess: Nokia E50)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
