your attachment got stripped, but i can imagine what it looks like. all runtime exceptions, wicket or not, are handled in the same way - redirect to the error page.
do you have a custom error page? if you do - if your error page has an error then what you describe might happen. -igor On Wed, Feb 11, 2009 at 6:49 AM, Anton Veretennikov <[email protected]> wrote: > Igor, > > Excuse me, but I really don't understand. > I'm asking about how to show Wicket error page. I thought that > throwing WicketRuntimeException will result in showing it. > > But I get SERVER error page. I attached an image to clarify matters. > > And error below is seen in Tomcat output, not in Wicket error page: > > ERROR - WicketFilter - closing the buffer error > java.lang.IllegalStateException: getOutputStream() has already been > called for this response > .... > > On Wed, Feb 11, 2009 at 5:20 AM, Marcelo Morales > <[email protected]> wrote: >> On Tue, Feb 10, 2009 at 5:00 PM, Igor Vaynberg <[email protected]> >> wrote: >>> the status code and the error page are orthogonal. you should still >>> see the standard error page, its just that it is returned with status >>> 500. >> ... with a proper browser (a cent) >> -- >> Marcelo Morales >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
