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. > > This is something that has bitten me quite often: putting debug println > statements in my code, and not seeing the results. Only to discover that the > method never got called in the first place. > > Martijn > > > On 3/31/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > > > > > > > > > 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 > > > > > > > > -- > Wicket 1.2 is coming! Write Ajax applications without touching JavaScript! > -- http://wicketframework.org ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
