Robert Burrell Donkin ha scritto:
On Mon, Sep 1, 2008 at 2:30 PM, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
Robert Burrell Donkin ha scritto:
On Sun, Aug 31, 2008 at 6:13 PM, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
Robert Burrell Donkin ha scritto:

<snip>

i'm not sure it's worthwhile to create yet another logger bridge in
this case. injecting a JCL log is probably good enough.
My issue with JCL injecting is that Logger does not have a
getChildLogger.
yes - that's probably the biggest mistake we made when creating the
API. then again, the JEE specifications weren't broken at that time so
it didn't seem necessary to cater for injecting loggers.
OT: why not to starting a commons-logging 2.0 that has this feature?

1. ceki already did

Do you speak about ILoggerFactory in slf4j or something else?

2. JCL's good enough so nothing else is ever to reach critical mass

Joerg Hohwiller crusade to add a new extended interface for the Ioc friendly logger (e.g: IoCLogger) was not so bad. This could have been easy even in a minor release and it could have been added to api only at first.

3. really the JCP should just get ceki to create a decent logging API

true, but I don't expect a "java.util.newlogging" ever..

4. i've wasted too many hundreds of hours on logging already

I understood this while looking markmail for this getChildLogger issue!
Thank you!

Interesting! It's cool to know that someone else see things like me :-)

http://markmail.org/message/4hlquicqcyovfv6a
http://markmail.org/message/ynsu2uutkh2z7mfp

Expecially http://markmail.org/message/3lnqomomugq3xyec

I see at the end of 2005 there was a patch to add getChildLogger and a discussion about releasing and then add it, but I didn't found what happened then. I guess it simply died or you found blocking issues... it's a pity.

Stefano

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

Reply via email to