Sorry. I've realized that maybe you need a more efficient strategy to
hide your parameter. I think that using a custom request handler is the
right way. you can override getExceptionMapperProvider in you
application to return tour custom handler for exception. You can have a
look at DefaultExceptionMapper to find some implementation hints.
hi,
maybe you can use a custom error page:
Application.getApplicationSettings().setInternalErrorPage
We have a secret parameter that we don't want to be logged in a stack
trace
or anything. Right now we're using a custom IRequestHandler to
intercept the
exception but I'm wondering if there's a more elegant way to do this.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Page-Parameters-logging-tp4668053.html
Sent from the Users forum 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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
