> -----Original Message-----
> From: Berin Loritsch [mailto:[EMAIL PROTECTED]]
> Sent: den 18 september 2002 17:18
> To: Avalon Developers List
> Subject: Re: Context Keys Proposal Change
>
>
> 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.
Should that really be passed in via the context? I'd prefer a
configuration entry or:
public interface Nameable {
public void setName (String name);
}
/LS
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
