yes, i recall. http://www.mail-archive.com/james-dev@jakarta.apache.org/msg01629.html
i am running James 2.0a3 - the latest 'stable' version. to implement the changes described i would bump up to the later version of avalon i suppose, and with a quick review of this xml config file, it appears that a lot has changed with reference to the logging. the avalon framework is great; the logging mechanism for it's components is great too; the interdependencies between avalon and james is not so great. in a sense, these logging issues really belong with avalon and not with james, so, i can configure *avalon* "... to log all messages to a single file, if it helps. Examples have been posted to this mailing list several times before." that is if i understand 'avalon' correctly in being an application server to launch other applications .... and to that i will and i am sure most of the issues i am facing will go away. however, has this new avalon been tested enough with james so we can call it "stable", or is this really a non-issue ?? alan -----Original Message----- > these multiple log files are not very informative nor consistant. You can configure James to log all messages to a single file, if it helps. Examples have been posted to this mailing list several times before. Steve
<<attachment: winmail.dat>>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
