Stephen McConnell wrote:
>
>
> Berin Loritsch wrote:
>> In fact, that is prefered to explicitly setting the category because
>> logging is performed within the scope that the container wants it
>> performed.
>>
>> I still don't see any *compelling* reason to expose the component's
>> name to itself.
>
>
>
> It is useful with respect to exception management. If you have
> exceptions that are passed from one system to another, it is desirable
> to pass information on which a reasonably elegant message can be
> generated on a remote system. This message is outside any logging
> context and naming strucrture implied by a containment hierachy.
> Cheers, Steve.
Ok. That is a compelling enough reason.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
