Comments on: Slf4j Logging Enables Your Grails Apps To Avoid isDebugEnabled Code Clutter and String Creation Overhead http://buildchimp.com/wordpress/?p=290 How-to's and Opinions on Release Engineering, Build Automation, and Groovy/Grails Development Sun, 20 Jun 2010 03:30:49 -0400 http://wordpress.org/?v=2.8.5 hourly 1 By: admin http://buildchimp.com/wordpress/?p=290&cpage=1#comment-2253 admin Wed, 30 Dec 2009 04:01:48 +0000 http://buildchimp.com/wordpress/?p=290#comment-2253 well.. I certainly agree with you that isDebugEnabled clutters up one's code ! Thanks for reading... - c/b well.. I certainly agree with you that isDebugEnabled clutters up one’s code !

Thanks for reading…
– c/b

]]> By: John Smith http://buildchimp.com/wordpress/?p=290&cpage=1#comment-2249 John Smith Wed, 30 Dec 2009 03:42:48 +0000 http://buildchimp.com/wordpress/?p=290#comment-2249 "Using ‘isDebugEnabled’ to wrap logging statements that involve String concatenation is standard Java best practice, especially in loop" No it isn't. 99% percent of the time, all it does is clutter up the code. It should only be used rarely. Only when you are logging huge object graphs. “Using ‘isDebugEnabled’ to wrap logging statements that involve String concatenation is standard Java best practice, especially in loop”

No it isn’t. 99% percent of the time, all it does is clutter up the code. It should only be used rarely. Only when you are logging huge object graphs.

]]>