On 4/3/02 3:04 PM, "Morgan Delagrange" <[EMAIL PROTECTED]> wrote:
> > ----- Original Message ----- > From: "Geir Magnusson Jr." <[EMAIL PROTECTED]> > To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]> > Sent: Wednesday, April 03, 2002 1:41 PM > Subject: Re: [logging] Need interface... > > >> On 4/3/02 2:32 PM, "Berin Loritsch" <[EMAIL PROTECTED]> wrote: >> >>>> -----Original Message----- >>>> From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] >>>> >>>> >>>> On Wed, 3 Apr 2002 [EMAIL PROTECTED] wrote: >>>> >>>>> >>>>> The current model used in log4j, jdk1.4, etc is pull - you >>>> request a >>>>> logger by name. Same thing for jdbc connections, resources, etc. >>>>> >>>> >>>> In fact, there's an important philosophical issue about >>>> logging here as well -- who gets to choose the name of the >>>> logger (and therefore the log level)? >>> >>> In IoC based apps, the container. period. That is what IoC >>> is all about. The container (or manager) makes all the decisions >>> about the component. >> >> And that's not what seems to be the philosophy of commons logging. The >> component gets to choose, or that is how it appears. >> >> This is teaching me not to jump to conclusions :) >> > > I'm a little wary of adding an interface to commons-logging that _should > never be used_ inside of any other Commons component. If that interface > started popping up in our other components, that would be very bad, as it > would then imply/require that component to be used inside of an IoC > framework. First, I never said that it "_should never be used_ inside of any other Commons component." I said it doesn't *have* to be used. Are you sure that o.a.c.l isn't the first step towards yet another jakarta framework? As for IoC, what's the downside if a component *can* be used inside of an IoC framework? -- Geir Magnusson Jr. [EMAIL PROTECTED] System and Software Consulting Uncertainty breeds confusion and confusion breeds despair. - Ceki Gulcu -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
