[slf4j-dev] Review of slf4j

[Niclas Hedhman]

On Monday 09 May 2005 05:52, Ceki Gülcü wrote:
> At 23:38 5/8/2005, Ceki Gülcü wrote:
> >At 07:34 5/7/2005, Niclas Hedhman wrote:
> >>Yes, either in constructor or via some framework specific lookup
> >> mechanism.
>
> Or injection through a setter method?

true.


> >>This is a fairly important aspect of IoC frameworks.
> >>Effectively, the idea that each API provides its own discovery/lookup
> >>mechanism is the (really low) underlying reason for the JCL issue, but
> >> also many similar (but less frequent) ones.
>
> I don't think the above statement is entirely true.

Well, I acknowledge your disagreement ;o)  and since it will not be very 
fruitful to analyze this in depth.

> >>ULogger logger = LoggerFactory.getInstance( this ).getLogger( subdomain
> >> );
>
> Supplying the factory with the object requesting the logger is an
> interesting suggestion. As in,
>
>    ULogger logger = LoggerFactory.getInstance(this);
>
> This opens the door for new possibilities.

It helps a lot for the framework, and I think it could also lead to some 
crafty utilization (multi-dimensional hierarchies, for instance) of existing 
Logging systems as well.
I am glad you like it. (FYI, I used to use that way for other structurally 
organized systems in my apps before.)


Cheers
Niclas