You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Leo Sutic <le...@inspireinfrastructure.com> on 2001/11/07 11:29:52 UTC
Propagation of LogEnabled
Berin,
now that Loggable is deprecated, how do you intend for LogEnabled to take
its place? I am in particular thinking about the ExcaliburComponentManager.
It is LogKitManageable, even...
/LS
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Propagation of LogEnabled
Posted by Berin Loritsch <bl...@apache.org>.
Leo Sutic wrote:
>
> > -----Original Message-----
> > From: Berin Loritsch [mailto:bloritsch@apache.org]
> > Sent: den 7 november 2001 14:40
> > To: Avalon Developers List
> > Subject: Re: Propagation of LogEnabled
> >
> > As to LogKitManageable,
>
> Berin,
>
> would it be possible to have
<snip/>
> So we don't get Log4JManageable, Log4JManager, and so on...
It would be possible. And if you want to provide the Factories
to control Log4J or JSR47 logging, I am not going to stop you.
I will say that we should always give LogKit better treatment
than the others.
Kind of a value-add thing. "OK, you don't want to use LogKit?
Well you have to configure your Logging implementation yourself
then. Here is how it can hook in..."
I can see where it would be a nice thing to have though.
--
"Those who would trade liberty for
temporary security deserve neither"
- Benjamin Franklin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Propagation of LogEnabled
Posted by giacomo <gi...@apache.org>.
On Wed, 7 Nov 2001, giacomo wrote:
> On Wed, 7 Nov 2001, Leo Sutic wrote:
>
> >
> >
> > > -----Original Message-----
> > > From: Berin Loritsch [mailto:bloritsch@apache.org]
> > > Sent: den 7 november 2001 14:40
> > > To: Avalon Developers List
> > > Subject: Re: Propagation of LogEnabled
> > >
> > > As to LogKitManageable,
> >
> > Berin,
> >
> > would it be possible to have
> >
> > interface LogManageable {
> > ...
> > }
> >
> > interface LogKitManageable extends LogManageable {
> > ...
> > }
> >
> > and
> >
> > interface LogManager {
> > ...
> > }
> >
> > interface LogKitManager extends LogManager {
> > ...
> > }
> >
> > So we don't get Log4JManageable, Log4JManager, and so on...
>
> Oh, sure. Its time to make this RSN. I'll take care of it.
Sorry, this mail was sent unintentionally. There is not way to do it
because you'll need to rewrite all the factories for the underlying
Manager to keep track of different implementation of the concrete
logger.
Giacomo
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Propagation of LogEnabled
Posted by giacomo <gi...@apache.org>.
On Wed, 7 Nov 2001, Leo Sutic wrote:
>
>
> > -----Original Message-----
> > From: Berin Loritsch [mailto:bloritsch@apache.org]
> > Sent: den 7 november 2001 14:40
> > To: Avalon Developers List
> > Subject: Re: Propagation of LogEnabled
> >
> > As to LogKitManageable,
>
> Berin,
>
> would it be possible to have
>
> interface LogManageable {
> ...
> }
>
> interface LogKitManageable extends LogManageable {
> ...
> }
>
> and
>
> interface LogManager {
> ...
> }
>
> interface LogKitManager extends LogManager {
> ...
> }
>
> So we don't get Log4JManageable, Log4JManager, and so on...
Oh, sure. Its time to make this RSN. I'll take care of it.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Propagation of LogEnabled
Posted by Leo Sutic <le...@inspireinfrastructure.com>.
> -----Original Message-----
> From: Berin Loritsch [mailto:bloritsch@apache.org]
> Sent: den 7 november 2001 14:40
> To: Avalon Developers List
> Subject: Re: Propagation of LogEnabled
>
> As to LogKitManageable,
Berin,
would it be possible to have
interface LogManageable {
...
}
interface LogKitManageable extends LogManageable {
...
}
and
interface LogManager {
...
}
interface LogKitManager extends LogManager {
...
}
So we don't get Log4JManageable, Log4JManager, and so on...
/LS
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Propagation of LogEnabled
Posted by Berin Loritsch <bl...@apache.org>.
Leo Sutic wrote:
>
> Berin,
>
> now that Loggable is deprecated, how do you intend for LogEnabled to take
> its place? I am in particular thinking about the ExcaliburComponentManager.
> It is LogKitManageable, even...
All NEW components/blocks/etc. should use the LogEnabled interface and the
AbstractLogEnabled base class.
Due to our goal of being backwards compatible, we cannot go back and change
all the released Components with the new interface. This is especially true
of the ExcaliburComponentManager. It would not be able to give the proper
logger to Loggable classes because the new Logger classes are opaque.
As to LogKitManageable, we only commit to providing cool tools for the
Avalon suite--Having the ExcaliburComponentManager simply wrap the LogKit
Logger with the Avalon Logger is a perfectly good solution.
--
"Those who would trade liberty for
temporary security deserve neither"
- Benjamin Franklin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>