as far as i know in deployment mode we are only throwing an
InternalExceptionPage
on that page we don't give the exception.
johan
On 7/10/07, Ingram Chen [EMAIL PROTECTED] wrote:
This anonys me too.
IMHO I think by default, it should log error in development mode,
and keep silent in
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
Lowell Kirsh wrote:
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:
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
This anonys me too.
IMHO I think by default, it should log error in development mode,
and keep silent in deployment mode.
On 7/10/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
In my web app, when someone visits a page that doesn't exist (eg. by
manually mucking with the url), they might end
On 7/9/07, Ingram Chen [EMAIL PROTECTED] wrote:
This anonys me too.
IMHO I think by default, it should log error in development mode,
and keep silent in deployment mode.
Sounds reasonable. If someone wants to open a JIRA issue for it please...
Eelco
