I'll agree and since a lot of these additions screwed up the formatting this was just an exercise in wanking the code base. If INFO level message are showing up in any profile then the wrong level of logging if being used.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "David Jencks" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, February 09, 2002 5:39 PM Subject: Re: [JBoss-dev] CVS update: jboss/src/main/org/jboss/jms/jndi JMSProviderLo > IMHO this is excessive caution and bloated code. Lifecycle methods are not executed often enough to make any difference in anythings speed. > > I suggest our logging policy should be > > --anything on the invocation path should be debug or trace and should be guarded. > > --anything else should not be guarded. It's ok to guard debug or trace, just for consistency, but I can't see any reason to ever guard something that is not on a speed-critical path. > > _________________________________________________________ > View thread online: http://main.jboss.org/thread.jsp?forum=66&thread=5671 > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
