> If you want to you can send me your code reduced to the relevant ones.
Really appreciate the offer. Thanks! However, before I do that, I'd like to figure out how to establish a good debugging strategy so I can figure this out for myself. What do you do? Edit/compile/run and just inspect visually? Or do you set up JUnit or some kind of automated testing? Are there any "best practices" that have been suggested for debugging Wicket stuff? Also, is it possible to configure the error messages so that they give more details about the component tree? ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
