Huw, Might this also support reroutable loggers? A File based logger for a component could, under administrator control, be rerouted to a JMS based one. Perhaps 'addtion to' as well as 'alternative' are possible with a live configurable logger.
- Paul >I'd like to be able to control the logging levels (and maybe one day the log targets) >for Phoenix components, applications and blocks. Here's one scheme for doing it, but >its fairly intrusive so I'd like to get some feedback on it. > >1) Create a LogManager interface through which the logging level for a particular >Logger can be get and set. (attached) >2) Do an implementation for each supported logging package, e.g. >org.apache.avalon.framework.logger.LogKitManager, Log4JManager, etc >3) Add a method to the Logger interface to return the LogManager: > > /** > * Returns the log manager for this logger. It is used to get and set > * the loging priority > */ > public LogManager getLogManager(); > >The LogManager would then be exposed for management in the 'standard' way - for >Phoenix this would be a seperate topic for each exported object that is also >LogEnabled. > >Thoughts? > > > >------------------------------------------------------------------------ > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
