> -----Original Message----- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: 20 December 2001 21:17 > To: Avalon Developers List > Subject: Re: Avalon and J2EE : Best practices > > On 12/20/01 1:04 PM, "Vincent Massol" <[EMAIL PROTECTED]> wrote: > > > - In order to consistently do logging (with Log4J) and configuration > > (single system configuration file) in both J2EE component and Avalon > > components, we have done the following : > > > > * Created a Logger component, > > * Created a Configuration component (that uses properties file - I will > > submit it for Excalibur in beginning of January), > > * Defined an AbstractComponent class that is Composable, retrieve the > > Logger and Configuration components from the CM and offers 2 getters : > > Simply as a point of interest, in the course of looking at using Avalon > with > Turbine I did much the same in stratum (which is the refactoring of all > the > tools that have grown in turbine, a turbine commons of sorts) in order to > do > what need to do vis-à-vis logging and configuration. >
I guess there must have been a hard discussion at the beginning of Avalon to decide whether to promote logging and configuration as lifecycle interface rather than components ... ;-) In the service framework I had written (babel on sourceforge), I had decided to implement them as component but I had a BaseLog and BaseConfig classes which was used for all logging and configuration related to the Component Manager itself (because it is possible it fails before the logging service is initialized or if there is no logging service registered - same for the configuration). However, in the implementation, the logging and configuration components were actually using the BaseXXX classes. [snip] -Vincent -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
