On Mon, 2 Jul 2001, Berin Loritsch wrote:
> giacomo wrote:
> >
> > On Wed, 27 Jun 2001, Carsten Ziegeler wrote:
> >
> > > Hi C2ers,
> > >
> > > what do you think about enhancing the information logged to the
> > > cocoon.log?
> > > For debugging etc. it would help to have a better formatted
> > > time information, the current url request perhaps the current
> > > ip address of the client etc.
> > > So I would suggest to pass the current environment/objectModel
> > > to the logging methods and they can extract everything they
> > > need from it and log it.
> >
> > That wont work. You cannot extend the logging methods. You can write a
> > custom LogTarget. We have solved such things by having a LogTarget as a
> > Avalon Component which is put into work after the ComponentManager has
> > been initialized. But this only works for Configuration stuff. As the
> > Environment/objectModel are request dependant (not thread safe) but the
> > LogTarget is/should be ThreadSafe you have a problem.
> >
> > The other way is (IIRC) some contextStack you can push things upon and
> > have your LogTarget pop it off there. But also I don't know how this
> > works in a multi threaded environment like a Servlet.
>
> Whenever I get the opportunity, I want to augment the ExcaliburComponentManager
> to define log targets and such. That way we can have multiple files, etc.
> to split all the info into.
I think you should read/study the LogKit. There is everything you need
to do that. You don't have/want to augment the ComponentManager with
thing that doesn't belong to it. It's not the problem defining a
LogTarget as a component. It's a problem to change the LogTarget at the
right moment. And since it is not the responsability of the
componentmanager to setup and define a Logger you'll have to do it
somewhere in the normal code (outsite a component).
Giacomo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
