You can try a couple of things - turning the logging level for org.apache.wicket.* down to debug, for example. You can also put you app in development mode with web.xml, but I don't think that's going to help you here.
Hoenstly, a blank screen to me would mean that it may *not* be Wicket, since with a Wicket error, you'll get by default an internal error page. -- Jeremy Thomerson http://www.wickettraining.com On Tue, Feb 17, 2009 at 4:11 AM, Edwin Ansicodd <erik.g.hau...@gmail.com>wrote: > > Deploying my wicket web app on Geronimo, I'm getting errors that seem to be > somewhere in the wicket. Is there a way to turn on Wicket debugging? > > I know there are errors because when I click the submit button, my response > page is blank. Not how it's supposed to be. No exceptions or error > messages. I want to see what is happening at the wicket level. Is there > some type of screen that shows on the web page that can give debug info for > what's happening in the wicket layer? > -- > View this message in context: > http://www.nabble.com/Wicket-Geronimo-debugging---tp22054182p22054182.html > Sent from the Wicket - User 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 > >
