Hi, I'm just beginning with Wicket Development. I've been used to Java
development where, when I want to perform a quick test, I simply add a
sysout to see if a certain code segment is being reached eg.
System.out.println("Segment 1 reached") or to find out what is being
returned by a database call eg.
System.out.println(makeDatabasecall().toString()) and so on. I know this is
not the best way to debug code, but for minor projects, it makes sense to be
quick testing.But as Wicket needs everything to be serialized, adding sysouts breaks the code. What is the best "quick" way to perform simple variable value checks (and print them out on a console/UI) using Wicket? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Best-Way-to-Perform-a-Quick-Test-tp4657669.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
