On Fri, 6 Sep 2002 23:50, Berin Loritsch wrote: > > From: Michael Melhem [mailto:[EMAIL PROTECTED]] > > > > Hi, > > > > Is there a reason > > org.apache.avalon.excalibur.monitor.Resource does not extend > > from AbstractLogEnabled?? > > Yep. It's just one more thing the user has to remember. The > Resource is a local object designed to represent a resource--with > the proper methods to obtain it. Therefore, I suggest we allow > for an alternate constructor: > > Resource( org.apache.avalon.logger.Logger ); > > If supplied, we will use it--otherwise we default to the > NullLogger.
I would prefer that you had an alternative implementation altogether that was Avalon aware. Maybe something like monitor.AvalonAwareResource ? If memory serves me well the only things that linked against Avalon/Framework was the monitor implementations. One thing I have been meaning to do for a while is decouple that package from Framework so that you have something like monitor.impl.ActiveMonitor monitor.impl.PassiveMonitor monitor.ActiveMonitor extends monitor.impl.ActiveMonitor (and adds avalon stuff) monitor.PassiveMonitor extends monitor.impl.PassiveMonitor (and adds avalon stuff) That way the package is lower coupling and should be easier to work with in future. Especially in situations (like in phoenix and myrmidon) where the specific configuration mechanism is innapropraite and easier to use them as just beans. Thoughts? -- Cheers, Peter Donald ----------------------------------------------------------------------- | I thought there was a knob on the TV to turn up the intelligence. | | There's a knob called "brightness", but it doesn't work. | ----------------------------------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
