Hi all, I'm planning to resolve WODEN-71 [1] and this is related to AXIS2-4334 [2] issue too. There are two good candidates here SLF4J [3] and Log4J [4] , i have went through the both if them but still my mind is swing between these two for best selection.
Option 1- SLF4J If we consider Woden project as alone SLF4J is the best way to handle this ,SLF4J free from problems available with JCL and enable users to select their convenient logging implementation while SLF4J only act as a Facade. Since Woden is a utility project providing such flexibility is a good feature. The main drawback is need to add at least 3 jars to Classpath slf4j-api , slf-Binding and actual logger implementation jar file. As a example if some one want to use SLF4J with Log4J he have to add slf4j-api.jar ,slf4j-log4j.jar together with log4j.jar. Logging is a important feature but in our case it is not a core feature of Woden , so I think asking users to add three new dependencies only because of longing is decrease the usability of Woden. Option 2- Log4J Log4J also free from those Class loading issues of JCL and users need to add only one jar file (log4j.jar) as a new dependency. But main drawback is we loose the flexibility and force users to use log4j as the logging framework. Guys. please provide your feedbacks about these two options ? [1] - http://issues.apache.org/jira/browse/WODEN-71 [2]- https://issues.apache.org/jira/browse/AXIS2-4334 [3]- http://www.slf4j.org/ [4] - http://logging.apache.org/log4j/ Thanks , -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://people.apache.org/~sagara/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
