Customising Error Pages

Unlike the Concerto application server, Active Web allows the developer to specify their own web page that should be executed when the Active Web servlet encounters an error.

It is possible to configure five custom error pages: Not Found, Page Load Failure; Aborted Page, Runtime Error and Redirect Failure; they are configured using the servlet parameters described above.

The value of the parameter is the path of URL to be executed from the current context root. For example in a default installation of Active Web the not found error page is /xadmin/resources/notfounderror.xsp. The following table outlines the different parameter names and values passed to the pages allowing customization of each error page.

Error Page	Parameters
not_found_error_page	msg – the not found error message Default Page: /xadmin/resources/notfounderror.xsp
runtime_error_page	msg – the runtime error message Default Page: /xadmin/resources/runerror.xsp
load_error_page	realuri – the uri that is being executed taking into account any possible secondary path resolution reqpath – the uri path requested of the Active Web servlet. This is likely to be the same as realuri unless secondary path processing is being used. errmsg – the error message describing the load error Default Page: /xadmin/resources/loaderror.xsp
redirect_error_page	redirect – the redirect error message Default Page: /xadmin/resources/redirecterror.xsp
aborted_process_error_page	uri – the uri that is was being executed but did not completed within the permitted runtime. Default Page: /xadmin/resources/pageaborted.xsp

Should an error occur processing an error page then a built in page will be displayed.