[slf4j-user] Why is LoggerFactory class now in API?
Martin Jericho
mart1041 at yahoo.com.au
Sat Mar 10 09:27:05 CET 2007
I would like to use SLF4J in my library, but am a little confused about one
aspect of it.
Why is the LoggerFactory class included in the API jar?
A discussion thread from Jan 31 titled "Using Using slf4j in a library
project" actually says that it is NOT included, and explains why. This all
makes sense, but why is it now included?
The next question is, when an application includes both the api and
implementation jars, how does the classloader know to use the LoggerFactory
in the implementation? I'm a little ignorant when it comes to how
classloaders work, but always thought that the system classloader uses the
first class it finds in the classpath. But even when I specify the api jar
first in the classpath, it still knows to use the LoggerFactory from the
implementation jar. Can someone explain how this works?
Thanks in advance
Martin
Send instant messages to your online friends http://au.messenger.yahoo.com
More information about the slf4j-user
mailing list