Possibility 1:  What does the Wicket application have to do to pass the System.out.println() statements?

 

Possibility 2:  If it’s not off-topic, could someone please give me a hint what I might have done wrong in configuring Tomcat?  I didn’t actually configure it myself; I took the easy way out and downloaded a “configured-for-development” version from:   http://www.coreservlets.com/Apache-Tomcat-Tutorial/

 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martijn Dashorst
Sent: Friday, March 31, 2006 3:22 PM
To: wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user] Wicket/Tomcat configuration: Where is System.out ???

 

There are 2 possibilities:

1. the application doesn't pass the system.out.println() statements
2. you didn't configure tomcat right.

usually tomcat spits out the system.out into the logs/ subdirectory, or on the console itself where it starts. if you run on linux, you'll have to redirect that output to a log file.

Martijn

On 3/31/06, Frank Silbermann <[EMAIL PROTECTED]> wrote:

To debug an application I've inserted a System.out.println command.  Where is System.out when I'm running Wicket on Tomcat?  Is it captured by some special Wicket logfile (I can't find any)?  It doesn't seem to be going to any of the Tomcat logfiles that I can see, nor to the console window (unless I'm just missing it).\

 

Is this something I have to configure in Tomcat to see the output of System.out?

 

Reply via email to