The most appealing feature to me is the parametrized log messages, and there is no need to wrap statements in if(log.isDebugEnabled()), isInfoEnabled() and so on.
On Fri, Jan 24, 2014 at 9:21 PM, Afkham Azeez <[email protected]> wrote: > http://glauche.de/2009/09/09/java-util-logging-vs-slf4j/ > > We should go with SLF4J > > > On Fri, Jan 24, 2014 at 8:59 PM, Sagara Gunathunga <[email protected]>wrote: > >> >> >> I'm not quite sure whether we can really compare SLF4J with Log4J where >> SLF4J is a logging API while Log4J is a logging implementation ( Log4J can >> be used with SLF4J and most common SLF4J binding as well), instead we >> should compare SLF4J API with Commons-Logging API. In my POV recent >> versions of both SLF4J and Commons-Logging are more or less similar. I >> don't have any objection to use SLF4J but have we consider JUL ? >> >> >> Please refer required dependencies for each option. >> >> - Commons-logging - Need 2 dependencies on runtime as Commons-logging >> API and implementation ( e.g - SLF4J API, Commons-logging-LOG4J bridge) >> - SLF4J - Need 3 dependencies on run time as SLF4J >> API, SLF4J-X binding, X logging framework ( e.g - SLF4J API, SLF4J-LOG4J >> binding , LOG4J ) >> - JUL - 0 dependencies just JDK >> >> If there is no found limitations I would prefer to use JUL and worth to >> consider it before make a conclusion. >> >> Thanks ! >> >> >> On Fri, Jan 24, 2014 at 6:26 PM, Afkham Azeez <[email protected]> wrote: >> >>> I was reading >>> http://javarevisited.blogspot.com/2013/08/why-use-sl4j-over-log4j-for-logging-in.html&; >>> we could remove a lot of boiler plate code, and bring in any logging >>> implementation if we use SLF4J. Thoughts? >>> >>> -- >>> *Afkham Azeez* >>> Director of Architecture; WSO2, Inc.; http://wso2.com >>> Member; Apache Software Foundation; http://www.apache.org/ >>> * <http://www.apache.org/>* >>> *email: **[email protected]* <[email protected]> >>> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: * >>> *http://blog.afkham.org* <http://blog.afkham.org> >>> *twitter: >>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez >>> <http://lk.linkedin.com/in/afkhamazeez>* >>> >>> *Lean . Enterprise . Middleware* >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Sagara Gunathunga >> >> Senior Technical Lead; WSO2, Inc.; http://wso2.com >> V.P Apache Web Services; http://ws.apache.org/ >> Linkedin; http://www.linkedin.com/in/ssagara >> Blog ; http://ssagara.blogspot.com >> >> > > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>* > *email: **[email protected]* <[email protected]> > * cell: +94 77 3320919 <%2B94%2077%203320919> blog: * > *http://blog.afkham.org* <http://blog.afkham.org> > *twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> > * linked-in: **http://lk.linkedin.com/in/afkhamazeez > <http://lk.linkedin.com/in/afkhamazeez>* > > *Lean . Enterprise . Middleware* > -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>* *email: **[email protected]* <[email protected]> * cell: +94 77 3320919 blog: **http://blog.afkham.org*<http://blog.afkham.org> *twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez <http://lk.linkedin.com/in/afkhamazeez>* *Lean . Enterprise . Middleware*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
