Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 29135 invoked from network); 8 Nov 1999 22:00:11 -0000 Received: from impactonline.org (impact@192.41.17.70) by apache.org with SMTP; 8 Nov 1999 22:00:11 -0000 Received: from perdues.com (adsl-216-101-185-43.dsl.snfc21.pacbell.net [216.101.185.43]) by impactonline.org (8.8.5) id OAA14278; Mon, 8 Nov 1999 14:59:53 -0700 (MST) Message-ID: <38274738.62ED7790@perdues.com> Date: Mon, 08 Nov 1999 13:57:12 -0800 From: Cris Perdue X-Mailer: Mozilla 4.5 [en] (Win95; U) X-Accept-Language: en,sr MIME-Version: 1.0 To: tomcat-dev@jakarta.apache.org Subject: Re: Debugging........ References: <002601bf29ad$46f0cb10$64646464@avnl1.nj.home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > i am sorry if this has been discussed before. > has there been any decision/discussion to add servlet debugging facility. > Don't know about discussion here, but I've found it quite helpful to have various flags, for example per-class, in a Servlet engine, that turn on logging of various routine information by the engine itself. I have a farily general-purpose servlet control panel to turn these on and off. I've found logging of request, headers, response headers, and specifically cookie information particularly helpful. I would be happy to contribute code that uses reflection to turn flags on and off. If Jakarta configuration is very dynamic, that could be another way to go. -- Cris Perdue Impact Online, Inc. http://www.volunteermatch.org