james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "robert burrell donkin" <robertburrelldon...@gmail.com>
Subject [POLL][modularisation] What About AbstractLogEnabled...?
Date Sun, 11 Mar 2007 08:15:26 GMT
one of the aims of the modularisation is to factor out the container
dependency into the deployment module. function, library and api code
should be container agnostic. this should make the code base more
approachable and allow the development of other container options.

one of the major issues that's going to need to be decided is logging.
ATM JAMES mostly uses AbstractLogEnabled for logging. this introduces
a deep coupling to the avalon framework.

a couple of reasonable options:

* accept that JAMES is coupled to avalon framework through the logging API
* create a lighter JAMES specific replacement for AbstractLogEnabled.
code in non-deployment modules extends that class. code in the
deployment module (whether through byte code enhancement or manual
subclassing) retrofits a logging aspect adapted to the framework.

opinions?

- robert

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message