On 4/3/02 2:53 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> On Wed, 3 Apr 2002, Geir Magnusson Jr. wrote: > >>> Why ? The lifecycle is not our problem - the interface just defines who a >>> component can be configured/managed from logging perspective. >>> >>> I agree the concept is a bit broken, as a component could use multiple >>> log channels - and the interface doesn't support that. >>> >>> Geir ? >> >> >> When you say multiple log channels, what do you mean? > > A component can log in multiple places and different informations. > > For example in tomcat it can log to access.log, error.log and possibly > other logs. > > And it may use different loggers for different kinds of information - so > you can fine tune the debugging ( use a different logger for different > areas of the code that you want to debug / tune independently ) > > For most components one logger is enough, but that's not allways the case. And to think that the logging project was to prevent components from having to use 'System.out.println' :) > > All the channels and properties are managed by the logger > implementation, and commons-logging explicitely doesn't cover that. > Thre is already an API for management, and each logger impl has a specific > way to configure. > > Costin > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- Geir Magnusson Jr. [EMAIL PROTECTED] System and Software Consulting "He who throws mud only loses ground." - Fat Albert -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
