Hi Seema, It might be possible but I haven't done it myself. It might be possible to construct the same page (using the page class) and use it instead of the ErrorPage? If you look at the handleException method you might be able to modify it to your needs?
On the other hand why not use a BorderPage to handle the common error handling? Hopefully in a future release Click would use an interface instead of an ErrorPage concept which would have worked nicely for your use case. regards Bob On Tue, Mar 13, 2012 at 3:56 AM, seemarich <[email protected]> wrote: > hi Bob, > > I'm able to catch the exception in my page class and generate a formatted > error message which I display to the user. This code is common in every page > and hence I did not want to repeat it in every page class. What I was trying > to do is handle this centrally by overriding the handleException method of > ClickServlet and put the error message generation code there and set it into > a bindable variable of the page object which caused the exception (so that > it can be displayed to the user). However, I'm not able to navigate to the > same page and show the message. Is there any way to achieve this? > > Thanks, > Seema > > -- > View this message in context: > http://click.1134972.n2.nabble.com/Re-Exception-handling-tp7365787p7367351.html > Sent from the click-development mailing list archive at Nabble.com.
