in production you shouldn't give users exceptions
then they know exactly what you run and then it is much easier to try to
hack something
exception in in production environments should be get from the log.
So you could set your own InternalError page create an extra log entry with
more info (current users and so on)
then you have that besides each other in the log.
johan
On 5/8/07, Bart Molenkamp <[EMAIL PROTECTED]> wrote:
I didn't know it was just there for debugging. I think it is useful for
production as well because it shows a stacktrace (and the
InternalErrorPage can't show it).
Is there any way to access the exception from an internal error page? If
so then InternalErrorPage is good for me too.
Bart.
Johan Compagner wrote:
> I think we had that method on application but that was moved again.
>
> But why do you want to change the ExceptionErrorPage?
> That is just there for debugging, Normally in production you would see
the
> InternalErrorPage
> that can be set through the settings.
>
> johan
>
>
> On 5/8/07, Bart Molenkamp <[EMAIL PROTECTED]> wrote:
>>
>> Hi,
>>
>> I think it's currently too hard to show a custom exception page. To do
>> so, I need to override Application.getRequestCycleFactory(), return my
>> own IRequestCycleFactory implementation, that can build my subclass of
>> WebRequestCycle that overrides the onRuntimeException() method.
>>
>> Maybe it's easier to define a method on WebApplication:
>>
>> Page onRuntimeException(Page page, RuntimeException e) {
>> return null;
>> }
>>
>> And call this method from WebRequestCycle.onRuntimeException. By
default
>> this would have the same behavior as it is implemented now, but it's
>> much easier to create a custom error page because I only have to
>> override onRuntimeException in my WebApplication subclass.
>>
>> Bart.
>>
>
