> In my web app, when someone visits a page that doesn't exist (eg. by > manually mucking with the url), they might end up at an error page > with a stack trace, and also when that happens, wicket logs an ERROR > like: "ERROR [RequestCycle] - Unable to load class with name: > com.foo.bar". I don't like that this is an ERROR, since our monitoring > picks it up and will send spurious warning emails to our team. Is > there a better way I can be dealing with this?
In Wicket 1.3 you can provide a custom request cycle and override RequestCycle#logRuntimeException 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
