If you set your application to be in deployment mode, that's what will happen.
Eelco
On 11/7/06, Lusebrink, Scott E CTR DISA GIG-CS
[EMAIL PROTECTED] wrote:
My project has a requirement to not show stack traces in production mode.
with
getApplicationSettings().setInternalErrorPage(ErrorPage.class);
set I still receive an Unexpected RuntimeException page with a full stack
trace, absolute path to the war and package structure, and the html template
file to the page.
Is the wicket Internal Error Page not the page i need to set so that i
NEVER see a wicket error page other than the one i defined.
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
