> -----Original Message-----
> From: Henning P. Schmiedehausen [mailto:[EMAIL PROTECTED] 
> Sent: Monday, August 18, 2003 3:55 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [PROPOSAL] Move Torque related classes to 
> seperate turbine module.
> 
> 
> I don't like the fact that components from the 
> AvalonComponentService can't and don't use Logging as 
> transparently as Turbine native service. I'd like to get some 
> sort of adapter that a container provides the components with 
> a logging facility a la commons-logging. I don't know whether 
> this is possible but getting one large log with just "avalon" 
> as facility and no class names (which IMHO only leads to 
> developers putting the class names into each and every 
> logging statement) is not desireable.

There is a way around this.  I seem to remember someone else patching one or
more of the fulcrum components that I converted to use the class name.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to