The internalerror page is for deployment so that that kind of information is not seen to the public. (that is not something you want)
You can specify you own nice formatted page for this ofcourse.
If you really do want something special you can override RequestCycle.onRuntimeException() That ofcourse works in all situations.
johan
On 3/22/06, Ingram Chen <[EMAIL PROTECTED]> wrote:
I tried, and it works well in deployment mode. thanks a lot.
But I think it's weird that it only works in deployment mode, how do I test this in development mode while developing ?On 3/22/06, Ingram Chen < [EMAIL PROTECTED]> wrote:Yeah.. I already tried IApplicationSettings.setIneternalErrorPage(), and still get
old exception page. Sounds like I need to try deploy mode again.
ThanksOn 3/22/06, Johan Compagner <[EMAIL PROTECTED]> wrote:that doesn't really replace our exception page when in development mode.
The best thing to do is implement/override RequestCycle.onRuntimeException()
johanOn 3/22/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:take a look at IApplicationSettings.setIneternalErrorPage()
-IgorOn 3/22/06, Ingram Chen <[EMAIL PROTECTED] > wrote:When runtime exception throw, wicket show ExceptionErrorPage.
Can I custom this page ? I don't want end user to see internal stack trace..
--
Ingram Chen
Java [EMAIL PROTECTED]
Institue of BioMedical Sciences Academia Sinica Taiwan
blog: http://www.javaworld.com.tw/roller/page/ingramchen
--
Ingram Chen
Java [EMAIL PROTECTED]
Institue of BioMedical Sciences Academia Sinica Taiwan
blog: http://www.javaworld.com.tw/roller/page/ingramchen
--
Ingram Chen
Java [EMAIL PROTECTED]
Institue of BioMedical Sciences Academia Sinica Taiwan
blog: http://www.javaworld.com.tw/roller/page/ingramchen
