Diego, I faced the same dilemma some time back and found that the support for log4j was not fully implemented somewhere, but I can't remember if this was Excalibur or Phoenix. The situation may be better now. I ended up writing SyslogTarget and SyslogTargetFactory classes. I've attached them for your convenience...
Steve > -----Original Message----- > From: Diego Castillo [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 18, 2004 3:39 AM > To: [EMAIL PROTECTED] > Subject: James logs via syslog or Log4J > > > Hi all, > > I would like to configure James 2.1.3 to log via syslog. > > After studying the Avalon documentation, this is the closest > I have got, which still does not work. This is my > environment.xml file: [...] <factory type="datagram-target" > class="org.apache.avalon.excalibur.logger.factory.DatagramTarg > etFactory" > /> > [...] > <datagram-target id="log-target-id"> > <address hostname="localhost" port="514"/> > <format type="extended">%{message}</format> > </datagram-target> > [...] > > The problem is that I can not configure the syslog facility :( > > My second option is making James use Log4J, then configure > the standard SyslogAppender. I have followed instructions > from here: > http://www.mail-archive.com/[EMAIL PROTECTED]/ms g00333.htm l Unfortunately, I get the following Phoenix exception: Unknown log version specification Has anyone ever configured James to log either directly to syslog or via Log4J? Regards, Diego --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
