> 20:06:14,806 INFO [STDOUT] loggedOut - isVisible? true > 20:06:14,806 INFO [STDOUT] loggedIn - isVisible? false > 20:06:14,810 INFO [STDOUT] loggedOut - isVisible? true > 20:06:14,810 INFO [STDOUT] loggedOut - isVisible? true > 20:06:14,811 INFO [STDOUT] loggedOut - isVisible? true > 20:06:14,811 INFO [STDOUT] loggedIn - isVisible? false > 20:06:14,813 INFO [STDOUT] loggedIn - isVisible? false > 20:06:14,814 INFO [STDOUT] loggedOut - isVisible? true > 20:06:14,814 INFO [STDOUT] loggedOut - isVisible? true > 20:06:14,815 INFO [STDOUT] loggedOut - isVisible? true > 20:06:14,815 INFO [STDOUT] loggedOut - isVisible? true > 20:06:14,816 INFO [STDOUT] loggedIn - isVisible? false
It is typically way more efficient to use a debugger if you want to find out how/ when/ where/ why things happen. Here, rather than putting in those log statements, you could just set a break point on your isVisible implementation - and don't forget to start up in debugging mode ;) And while you're at it, be sure to attach the Wicket sources to your project dependencies, so that you can step into the Wicket code as well. This may be a bit intimidating at the start, but it's a great way to learn about the framework and I hope coding in general :) Cheers, Eelco ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
