Posts tagged with 'error-logging'
The quality of a website is not only judged by how well the website works but how gracefully it fails. When there is an error with ActiveReports it displays the error ( a stack trace ) in the web viewer in an alert box style box but leaves you as the developer limited in how you can handle the error or log the error. It is important to point out that an "Error" needs to be handled in different ways. We need to let the user know that there is a problem but we don't want to inform them via a stack dump. It is vice versa for the developers, they don't care that an error happened per se, but they are interested in what caused the error. Luckily we can completely customize the way we handle application errors in ActiveReports. Let's think of a scenario, you have a large website that integrates ActiveReports into it. Let's say our ActiveReports connects to a server to get its data. We, as developers, cannot be promised that the connection to our Database will always be valid, for many reasons outside our control. If our website loses connection to its database server, we don't want our Users to suffer from it by simply giving them a stack dump or a server error. We want to provide our users with ways to get assistance in resolving the issue. Also, we don't want our users knowing that there is an issue with the DB connection, we simply want to let them know that there is an issue and they can contact customer support to report the issue and get it resolved.