This content has been marked as final.
Show 4 replies
-
1. Re: JBAS-2112 - nlog4j
adrian.brock Aug 12, 2005 12:22 PM (in response to adrian.brock)And we still have some minor issues that might have been caused by
previous upgrades of log4j
http://jira.jboss.com/jira/browse/JBAS-1851
e.g. This does not (no longer?) works<appender name="SYSLOG" class="org.apache.log4j.net.SyslogAppender"> <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/> <param name="Facility" value="LOCAL7"/> <param name="FacilityPrinting" value="true"/> <param name="SyslogHost" value="localhost"/> </appender>
It is missing mandatory configuration that causes an NPE. -
2. Re: JBAS-2112 - nlog4j
elkner Aug 12, 2005 4:36 PM (in response to adrian.brock)"adrian@jboss.org" wrote:
e.g. This does not (no longer?) works<appender .../>
It is missing mandatory configuration that causes an NPE.
Yes, it needs a layout section. But this is an issue for the already used log4j-1.2.8.jar as well. -
3. Re: JBAS-2112 - nlog4j
adrian.brock Aug 12, 2005 5:07 PM (in response to adrian.brock)"elkner" wrote:
Yes, it needs a layout section. But this is an issue for the already used log4j-1.2.8.jar as well.
Yes it is. But my point was that it might have been broken by a previous upgrade
I didn't investigate whether this worked at any point in the past?
We only have it is an example, but somebody else will have been using it,
so we broke their config.
P.S. It would be good if it gave a more meaningful error message than NPE. ;-P -
4. Re: JBAS-2112 - nlog4j
elkner Aug 12, 2005 5:27 PM (in response to adrian.brock)"adrian@jboss.org" wrote:
It might be true that JBoss using slf4j will speed the adoption of that project, but it will also slow the adoption of new JBoss releases if it breaks existing applications.
Yepp, and that's why I think nlog4j is well suited for this case - backward compat with log4j (so old stuff can still use log4j) and new apps can already start using the new API ...