harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexei Zakharov" <alexei.zakha...@gmail.com>
Subject Re: [classlib] logging from within our implementation
Date Thu, 08 Jun 2006 14:25:31 GMT
People, have compassion on critical error/info messages at least (>=
Level.WARNING) . This is not a DEBUG logging, this is useful stuff for
end user!

2006/6/8, Geir Magnusson Jr <geir@pobox.com>:
>
>
> Tim Ellison wrote:
> > Resurrecting this thread, with some trepidation...
> >
> > We went round the houses a bit, but did we reach a conclusion to the
> > questions you posed?
>
> Sadly, no, it doesn't seem so.
>
> I was hoping that Aspect-Master-George might give us some hints...
>
> >
> > I'm eager to fix-up the DNS provider code.
>
> Is there something driving that other than the desire to "put it to
> bed"?  (Just curious)
>
> Can you just comment the stuff out?  (or I can - I'll be happy to)
>
> geir
>
> >
> > Regards,
> > Tim
> >
> > Geir Magnusson Jr wrote:
> >> Seems like there is an important issue here, but the discussion can't
> >> seem to escape out of the thicket of the example.
> >>
> >> 1) Should we allow any logging from within the classlibrary?
> >>
> >> 2) How should we do it?
> >>
> >> There are a bunch of ways for the second question...  using j.u.l, using
> >>  IOC and injecting our own logging target to reduce dependencies and
> >> make people think before logging, using aspects?
> >>
> >> Comments?  We probably should try to get to a conclusion in general...
> >>
> >> geir



-- 
Alexei Zakharov,
Intel Middleware Product Division

---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org


Mime
View raw message