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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
