The culprit is the protected setupLogging() method in ApplicationServlet. It initialises log4j using Tapestry's settings from memory. We worked around it by overriding the method in our servlet subclass, and not invoking the super implementation. We are using 2.0.1 which is very close to 1.0.10 so this should work for you too, but YMMV...
Richard ----- Original Message ----- From: "Jim Birchfield" <[EMAIL PROTECTED]> To: "Tapestry Developer" <[EMAIL PROTECTED]> Sent: Thursday, June 27, 2002 7:21 AM Subject: [Tapestry-developer] Tapestry and Log4j > I am using 1.0.10 of Tapestry (I know, haven't upgraded yet). Whenever my > war containing my Tapestry application gets deployed, log4j simply stops > working. I can still see System.err, but something overrides all my log4j > properties. I have verified I am not including another log4j.properties > file in the war. Is there anything in Tapestry that overrides this? > > James Birchfield > Director, Application Development > Genscape, Inc. > (502) 583-2298 (o) > (502) 639-3136 (c) > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: Jabber Inc. > Don't miss the IM event of the season | Special offer for OSDN members! > JabberConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn > _______________________________________________ > Tapestry-developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/tapestry-developer > ------------------------------------------------------- This sf.net email is sponsored by: Jabber Inc. Don't miss the IM event of the season | Special offer for OSDN members! JabberConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
