only if you deploy your application in development mode. in deployment mode only the "internal error" page. see IApplicationSettings#setInternalErrorPage(Class)
gerolf Thanks for the good piece of info. I still do not see why the wicket should treat it as an internal error if there are missing parameters? I guess wicket needs to follow the same paradigm as in the raw HttpRequest, let the user pull the parameters if they exist and take their own decision if they do not. It does not make any sense for the Wicket to declare the state of emergency if the parameters key value do not match. -- View this message in context: http://www.nabble.com/Param-%3D-null-tf4413478.html#a12590866 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
