You should be able to add the following to your class and then call log.debug(message) and logging messages will show up in your console.
private final Log log = LogFactory.getLog(YourClass.class); Matt On Thu, Jun 18, 2009 at 2:52 PM, David Brown <dbr...@sexingtechnologies.com>wrote: > Hello appfuse folks, I have a very nice web app worked up from the > appfuse-wicket-ibatis-1.8.2 module and the efforts of Matt Raible. I have > been able to duplicate all of the necessary classes to implement my own > functionality similar to the: UserXXX.java classes. My version of these > classes is listing the records correctly from the IBatis-MySQL config. > However, when I click on a record to do so-called: edit-link the targeted > record the web-app blows up at my version of the UserModel.java (Object > load() method). I have source level debugged this but the app is blowing up > before I can examine any variables. None of the testcases are failing or > have errors. I am opting to just do some good-ol' logging. The BasePage > defines a logger but this is not available in the UserModel.class. > Suggestions as how to introduce logging without blowing up my web-app or > unduly impacting Matt's carefully designed architecture would be > appreciated. I am not a wicket expert so any ideas whatever will help. > Particulars follow. Please advise, David. > > > OS: Windows XP > JDK: 1.5 > Maven: 2.1.0 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net > For additional commands, e-mail: users-h...@appfuse.dev.java.net > >
