Here's a video on how to configure Eclipse to work with Wicket 1.5.x: http://www.youtube.com/watch?v=3fdiCBb4rK8
Not sure if it's in English but then again you get the point from watching the footage for 3 mins. Once you have your project up and running, you can run it in debug mode and step through your code line by line. ~ Thank you, Paul Bors On Mon, Apr 1, 2013 at 11:24 AM, Dan Retzlaff <[email protected]> wrote: > I think you misunderstand serialization. Only class member data is > serialized, plus a small amount of metadata like the class name and a > version. Normal methods, and any logging in those methods, have no effect > on serialized output. If you tried printing and it didn't work, please > share your code. > > On Mon, Apr 1, 2013 at 7:51 AM, madmax108 <[email protected]> wrote: > > > 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: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
