tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From August Detlefsen <augustd...@yahoo.com>
Subject Re: Debugging JSPs and Servlets
Date Wed, 27 Feb 2002 20:17:58 GMT
For the quick and dirty approach, you can put System.out.println()
statements in your code and find the output in:

TOMCAT_HOME/logs/catalina.out



--- Sriram Narayanan <sriramx_2000@yahoo.com> wrote:
> 2/27/02 11:17:26 PM, "Nitin Vira" <nvira@juniper.net> wrote:
> 
> >Hello,
> >
> >I am trying to create an environment that will assist in debugging
> jsps, i think one of the basic ways to do debugging is through
> logging, I want 
> to log various request coming in along with the request parameters, i
> checked the access loggs but they only logg GET request also it
> doesnt 
> logg the parameters, is there anyway i can logg POST request too
> along with the request parameters, i can possibly use a filter to do
> it, will that 
> be a right approach also can i configure a filter to run for all the
> servlets? Also is it possible to logg something like forwards to
> another page and 
> including other pages, also if you have any other suggestions to add
> features that will assist in debugging that i can implement i will
> greatly 
> appreciate it.
> >
> 
> Use Log4J. (http://jakarta.apache.org/log4j) 
> 
> Log4J has something called Logging Levels, e.g. DEBUG, ERROR, INFO
> etc...
> 
> Let's say you have some 15 packages with some 10 classes in each.
> 
> In each class, instantiate a Logger with the statement
> 
> static Logger logger = Logger.getInstance(MyClass.class.getName());
> 
> Now within the class, write both DEBUG level statements and INFO
> level statements:
> 
> e.g. 
> 
> public void someTask(String first, String second){
> 	logger.debug("just entered the someTask method, args are " + first +
> ":" + second);
> 	logger.info("about to calculate something");
> 	int x = calculate();
> 	logger.debug("the calculation result was " + x);
> }
> 
> Now, DEBUG levels happen to be lower in importance than INFO levels. 
> 
> Log4J can be instructed on which level to log via a properties file.
> So, you can change log levels, or even disable loggin altogether via
> an external properties file. No changes to the code are required at
> all.
> 
> Also, you can specify that the log outputs from a particular class
> should be redirected to one file, while all other logs could go to
> another file, or 
> even a JDBC target.
> 
> 
> >Thanks,
> >Nitin
> >
> 
> Sriram
> 
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> 
> --
> To unsubscribe:   <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
> For additional commands: <mailto:tomcat-user-help@jakarta.apache.org>
> Troubles with the list: <mailto:tomcat-user-owner@jakarta.apache.org>
> 


__________________________________________________
Do You Yahoo!?
Yahoo! Greetings - Send FREE e-cards for every occasion!
http://greetings.yahoo.com

--
To unsubscribe:   <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
For additional commands: <mailto:tomcat-user-help@jakarta.apache.org>
Troubles with the list: <mailto:tomcat-user-owner@jakarta.apache.org>


Mime
View raw message