How does slf4j bind to implementation? Does it really do so during compile time? -
in documentation slf4j says binding happens during complie time:
"slf4j not rely on special class loader machinery. in fact, each slf4j binding hardwired @ compile time use 1 , 1 specific logging framework. example, slf4j-log4j12-1.7.5.jar binding bound @ compile time use log4j. in code, in addition slf4j-api-1.7.5.jar, drop 1 , 1 binding of choice onto appropriate class path location. not place more 1 binding on class path. here graphical illustration of general idea." http://www.slf4j.org/manual.html
how work?
from have seen, expecting class staticloggingbinder in same package (org.slf4j.impl), regardless of implementation - finds in same place.
Comments
Post a Comment