> i am running James 2.0a3 - the latest 'stable' version. I've been running James 2.1-CVS. There have been a few defects introduced (and more fixed) along the way, but generally I'm finding that it is stable. Considering the defects present in 2.0a3 and fixed in James 2.1-CVS, I'm happier with the current code.
I've been running whatever version of Phoenix Paul Hammant felt best to keep
in the CVS for us. During the code testing period, Peter is proposing that
we try upgrading to the release version of Phoenix, et al, so that we don't
have a proprietary beta release.
> the avalon framework is great;
> the logging mechanism for it's components is great too;
Folks seem generally pleased with it.
> 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
..."
James is a client of Avalon's logging mechanisms. James is an "Avalon
application" or whatever terminology the Avalon folks want to use these
days. I'm not aware of any plans to decouple James from Avalon, although
there is an expressed desire to make James less coupled to any specific
Avalon container.
In james-server.xml/environment.xml, I believe that your best bet is to
change all of the log categories to reference the same log target. You
could change your log targets to all refer to the same file, but I would
worry about buffering/race conditions without prior knowledge of how they've
implemented that code.
--- Noel
<<attachment: winmail.dat>>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
