cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@s-und-n.de>
Subject RE: latest Excalibur breaks logging
Date Wed, 03 Apr 2002 06:49:29 GMT
Sorry for the trouble, it should be fixed now.

The new build system of avalon uses a different approach to ours: all
optional jar files are not in the cvs anymore (well not all but some
of the important ones like the servlet.jar etc.).

Carsten

> -----Original Message-----
> From: ovidiu@orion.rgv.hp.com [mailto:ovidiu@orion.rgv.hp.com]On Behalf
> Of Ovidiu Predescu
> Sent: Wednesday, April 03, 2002 12:34 AM
> To: giacomo; Carsten Ziegeler
> Cc: cocoon-dev@xml.apache.org
> Subject: Re: latest Excalibur breaks logging
>
>
> On Wed, 3 Apr 2002 00:06:31 +0200 (CEST), giacomo
> <giacomo@apache.org> wrote:
>
> > On Tue, 2 Apr 2002, Ovidiu Predescu wrote:
> >
> > > On Tue, 02 Apr 2002 23:35:10 +0200, Gianugo Rabellino
> <gianugo@apache.org> wrote:
> > >
> > > > Berin Loritsch wrote:
> > > >
> > > > > Ovidiu, if you built from CVS, then you must have the Servlet.jar
> > > > > file included in the lib directory to get that *optional* target.
> > > >
> > > >  >>Logging Error: Could not set up Cocoon Logger, will use
> screen instead
> > > >  >>org.apache.avalon.framework.configuration.ConfigurationExcepti
> > > >  >>on: cannot find LogTargetFactory class
> > > >  >>org.apache.avalon.excalibur.logger.factory.ServletTargetFactory
> > > >
> > > > Hmmm... I don't get it. I assume that this has to do with
> the Excalibur
> > > > build, not Cocoon's. The Excalibur jar in CVS is missing
> that class, so
> > > > whoever updates Excalibur jars should make sure that this
> optional class
> > > > is included, this is not a Cocoon build issue. Or am I
> missing something?
> > >
> > > Yes, you're right. The Excalibur jar file is missing the
> > > ServletTargetFactory class, and that's definitely not an issue with
> > > the servlet.jar file (which BTW is there in lib/optional/).
> > >
> > > Commenting out the second <factory> element in logkit.xconf solves the
> > > problem. As it turns out, the "servlet" factory is not even used in
> > > the Cocoon logkit setup, so it can be completely removed from this
> > > file. Should I commit this file?
> >
> > It was in logkit.xconf before the reshape of the logging configuration.
> > It seems disapeared. The intention was that every ERROR and above
> > message should also be logged into the servlet log.
>
> Ah, I see! Thanks for the clarification.
>
> I guess we need a new Excalibur with the ServletTargetFactory in it,
> before we can do anything, right? Carsten, can you please take a look
> at this?
>
> Thanks,
> Ovidiu


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message