[jbossws-dev] Experiments with LogMessage levels for jbossws/wfly
Hi.
Just sharing small experiment with counting of LogMessage for jbossws/wfly projects
grep -i @LogMessage jbossws-api jbossws-spi jbossws-common jbossws-common-tools
jbossws-cxf -R | cut -d@ -f2 | sort | uniq -c | sort -n
7 LogMessage(level = INFO)
19 LogMessage(level = ERROR)
22 LogMessage(level = TRACE)
31 LogMessage(level = DEBUG)
34 LogMessage(level = WARN)
Here is Wildfly:
grep -i @LogMessage wildfly-core wildfly -R | cut -d@ -f2 | sed
"s/Logger.Level.//g" | sed "s/Level.//g" | sed "s/l=/l =/g"
| sort | uniq -c | sort -n
1 LogMessage(level = FATAL)
14 LogMessage(level = TRACE)
27 LogMessage(level = DEBUG)
195 LogMessage(level = INFO)
253 LogMessage(level = ERROR)
320 LogMessage(level = WARN)
WLFY vs. JBWS usage of logging levels differ a bit. Is it something to worry about ?
FYI: Raw WildFly is a bit inconsistent :)
grep -i @LogMessage wildfly -R | cut -d@ -f2 | sort | uniq -c | sort -n
1 LogMessage(level = FATAL)
1 LogMessage(level= Logger.Level.INFO)
2 LogMessage(level = Logger.Level.DEBUG)
2 LogMessage(level= Logger.Level.ERROR)
3 LogMessage(level = Level.ERROR)
3 LogMessage(level = Level.INFO)
3 LogMessage(level = Logger.Level.INFO)
4 LogMessage(level = Level.WARN)
5 LogMessage(level = Logger.Level.ERROR)
10 LogMessage(level = Logger.Level.WARN)
14 LogMessage(level = TRACE)
23 LogMessage(level = DEBUG)
92 LogMessage(level = INFO)
118 LogMessage(level = ERROR)
164 LogMessage(level = WARN)
grep -i @LogMessage wildfly-core -R | cut -d@ -f2 | sort | uniq -c | sort -n
1 LogMessage(level = Level.DEBUG)
1 LogMessage(level = Logger.Level.DEBUG)
2 LogMessage(level = Logger.Level.INFO)
3 LogMessage(level = Logger.Level.ERROR)
10 LogMessage(level = Logger.Level.WARN)
33 LogMessage(level = Level.WARN)
34 LogMessage(level = Level.ERROR)
36 LogMessage(level = Level.INFO)
58 LogMessage(level = INFO)
88 LogMessage(level = ERROR)
99 LogMessage(level = WARN)
Rostislav