dont know. But logging has saved my skin many times. It is worth the effort to use log4j than putting lots of system.out.println statements. They become clumsy when you have some 10 servlets printing to the console...
-----Original Message----- From: Arnaud Héritier [mailto:[EMAIL PROTECTED]] Sent: Friday, October 19, 2001 10:56 AM To: '[EMAIL PROTECTED]' Subject: RE: Logging from a servlet in Tomcat One question about this subject. Why the Tomcat (4) team (Craig and others) didn't use log4J to trace the server ????? > -----Message d'origine----- > De: G.Nagarajan [SMTP:[EMAIL PROTECTED]] > Date: vendredi 19 octobre 2001 10:48 > À: [EMAIL PROTECTED] > Objet: RE: Logging from a servlet in Tomcat > > Best is to use Log4j for logging. It gives more control and > flexibility than using the servlet logging facility. > > -----Original Message----- > From: Barney Hamish [mailto:[EMAIL PROTECTED]] > Sent: Friday, October 19, 2001 10:42 AM > To: '[EMAIL PROTECTED]' > Subject: RE: Logging from a servlet in Tomcat > > > I haven't tried this in 4 but in 3 you can always just print to stdout or > stderr > eg. System.out.println("In the Foo function"); > Which will get printed to the console or your logs depending on how you're > running tomcat > > -----Original Message----- > From: Dr. Evil [mailto:[EMAIL PROTECTED]] > Sent: Friday, October 19, 2001 10:30 AM > To: [EMAIL PROTECTED] > Subject: Logging from a servlet in Tomcat > > > > I have a question: It would be extremely useful for a servlet to be > able to record debugging messages in some way. I don't have a Java > debugger, but I could do a lot of debugging if I had a command that > looked like this: > > log("We are in this part of the code now"); > > I have seen documentation for a command like that, and I have tried it > in my installation of Tomcat 4.0, but it doesn't send any output > anywhere, so it seems useless. Is there a way to get it to work? > > Thanks
