On Thu, 26 Apr 2007, Martijn Dashorst wrote: > > Any pointers? > > Depends on your application server. Tomcat logs everything in > catalina.out. Wicket typically logs all caught exceptions on error > level, so those shouldn't go unnoticed, unless you catch them yourself > without logging :) > > in your log4j config make sure you have the wicket category set to > info, warn or error.
That could have been the problem. I'm using Resin Opensource as my container in production, and did not have a log4j.properties file on my classpath. I'll try adding one and see if that helps. Thanks, Nick -- "Humans are a dangerously insane and very sick species." -- Eckhart Tolle This message has been brought to you by Nick Johnson 2.2 and the number 6. http://healerNick.com/ http://morons.org/ http://spatula.net/ ------------------------------------------------------------------------- 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
