Return-Path: 
 <cocoon-dev-return-25110-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 34879 invoked by uid 500); 2 Apr 2002 22:19:02 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 34847 invoked from network); 2 Apr 2002 22:19:01 -0000
From: "Berin Loritsch" <bloritsch@apache.org>
To: <cocoon-dev@xml.apache.org>,
	"'Gianugo Rabellino'" <gianugo@apache.org>
Subject: RE: latest Excalibur breaks logging 
Date: Tue, 2 Apr 2002 17:19:00 -0500
Message-ID: <004701c1da94$637bb070$ac00a8c0@Gabriel>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
In-Reply-To: <200204022157.g32LvGv27189@orion.rgv.hp.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

> -----Original Message-----
> From: ovidiu@orion.rgv.hp.com=20
>=20
> On Tue, 02 Apr 2002 23:35:10 +0200, Gianugo Rabellino=20
> <gianugo@apache.org> wrote:
>=20
> > Berin Loritsch wrote:
> >=20
> > > Ovidiu, if you built from CVS, then you must have the Servlet.jar=20
> > > file included in the lib directory to get that *optional* target.
> >=20
> >  >>Logging Error: Could not set up Cocoon Logger, will use screen=20
> > instead =20
> > >>org.apache.avalon.framework.configuration.ConfigurationExcepti
> >  >>on: cannot find LogTargetFactory class
> >  >>org.apache.avalon.excalibur.logger.factory.ServletTargetFactory
> >=20
> > Hmmm... I don't get it. I assume that this has to do with the=20
> > Excalibur
> > build, not Cocoon's. The Excalibur jar in CVS is missing=20
> that class, so=20
> > whoever updates Excalibur jars should make sure that this=20
> optional class=20
> > is included, this is not a Cocoon build issue. Or am I=20
> missing something?
>=20
> Yes, you're right. The Excalibur jar file is missing the=20
> ServletTargetFactory class, and that's definitely not an=20
> issue with the servlet.jar file (which BTW is there in lib/optional/).

Yes, but is it in Excalibur's lib directory?


> Commenting out the second <factory> element in logkit.xconf=20
> solves the problem. As it turns out, the "servlet" factory is=20
> not even used in the Cocoon logkit setup, so it can be=20
> completely removed from this file. Should I commit this file?

It used to be used to forward results to the Servlet's context.log()
method. on ERROR level messages.


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