|
|
|
|
This chapter presents new and improved methods that come with the Transaction Engine 3, methods that regard the errors handling from the server-side. This means that errors are detected and treated after submitting the page to the server. It also means that the result of the error-handling routines is displayed when reloading the page, and not immediately after the error occurs.
In order to maintain the values already submitted by the page through its forms, Transaction Engine 3 uses the transaction recordset . The recordset holds the values, so when an error occurs, data can and will be placed in the form, and the wrong field will be highlighted. This feature provides the user with the exact field that had the wrong input, and the developer with the right debug information.
When talking about debug modes, it is worth mentioning the two modes that Transaction Engine 3 comes with and that can be switched on the fly in order to hide or display complex details regarding the errors on page:
the Development mode - it provides a great amount of information, including the stack trace of all the operations (both executed and to-be-executed), with the errors marked; it also provides additional help and solutions;
the Production mode - it only displays a limited amount of information, being more suited for finished applications that are visited by the public.
Development Mode Error Handling