Hi Frank
I *think* system.out/err goes to catalina.out.
If you are using log4j, but happen to write a few system.outs, you might
want to do something like this in your Application class:
/* redirect stdout/stderr to log4j */
System.setOut(new PrintStream(new
To debug an application Ive inserted
a System.out.println command. Where is System.out
when Im running Wicket on Tomcat?
Is it captured by some special Wicket logfile
(I cant find any)? It doesnt
seem to be going to any of the Tomcat logfiles that I
can see, nor to the console window
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
on linux there is a catalina.out file that captures stdout, on windows there is no such file, it just goes to the console that you started tomcat from.-IgorOn 3/31/06,
Frank Silbermann [EMAIL PROTECTED] wrote:
To debug an application I've inserted
a System.out.println command.
Possibility 1: What does the Wicket application have to
do to pass the System.out.println() statements?this has nothing to do with wicket, this is only about how you configured tomcat.-Igor
You have to put the statements somewhere where you are sure they will be invoked. For instance, you might want to do System.out.println() in your page constructor. Or your application constructor.This is something that has bitten me quite often: putting debug println statements in my code, and not
Wicket does not capture any output. If you can't find it in your
output window, it should be in one of the log files.
Consider using a logging API (commons logging/ log4j or jdklogger)
instead of system printlns; it's more flexible in where you put it and
pushing everything through the same
Of course this happens while debugging too and can drive you nuts until you realize you've goofed.Since I use MyEclipse...I like to use println statements occasionally and just watch them roll by in the Console panel...you could do this w/ Netbeans or any other IDE, I'm sure. That is - if you're
Or just use a decent debugger :)
Eelco
On 3/31/06, Martijn Dashorst [EMAIL PROTECTED] wrote:
You have to put the statements somewhere where you are sure they will be
invoked. For instance, you might want to do System.out.println() in your
page constructor. Or your application constructor.
Sure, I do that too. Eclipse usually informs you whether that debugger
point actually is available/ reachable. If the debug statements are
informative by themselves, why not just use a logger API and turn on/
off whenver you want?
Eelco
On 3/31/06, Vincent Jenks [EMAIL PROTECTED] wrote:
Of
10 matches
Mail list logo
