james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Danny Angus" <da...@apache.org>
Subject RE: [PATCH] SMTPHandler logging
Date Tue, 08 Oct 2002 08:10:35 GMT
> 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,
> there is an expressed desire to make James less coupled to any specific
> Avalon container.

I think the desire is best seen not as to completely de-couple James but
to replace some of the services which are provided by Avalon cornerstone
and excalibur by ones which James can provide itself, specifically such as
file repositories. In many cases this work is not abandoning Avalon so
much as providing added value to James.
James is unlikely to abandon Avalon Framework, unless there are
revolutionary changes which James can't assimilate, nor is James likely to
abandon Phoenix in the short term.
What we would like to do is to future proof James against revolutionary
changes in our Avalon dependancies, and control the code for services ,
currently provided by Avalon code, in which James Users are logging real
and significant usability/functionality issues.

Thats my take on this discussion anyway.


View raw message