Error Handling

From Daxipedia

Contents 1 Description 2 Handling errors 2.1 4D based 2.1.1 Critical errors 2.1.2 Other errors 2.2 Browser based 3 Trapping errors 4 Third party integration 4.1 Firebug and Firebug Lite 4.2 Safari console

[edit] Description

[edit] Handling errors

[edit] 4D based

[edit] Critical errors

Critical errors will refresh the page.

Following errors are considered critical:

1. Invalid Access Point
2. Invalid Session Id - session id is expired or invalid.

[edit] Other errors

Other errors will be silently displayed in the console, which can be opened via button on the sidebar if user is logged in as administrator, or via showDebugger command. Check Console entry for more information on console.

[edit] Browser based

Browser based errors are triggered by browser, which are most often Javascript errors.

[edit] Trapping errors

Developer can trap for errors in fourdaf_dev_errorTrap function located in callbacks.js function.

Parameters received:

1. type - error type, can be 4D or browser.
2. hint - error hint sent by 4D.
3. message - error message sent by 4D.

fourdaf_dev_errorTrap (type, hint, message) {


}

[edit] Third party integration

[edit] Firebug and Firebug Lite

If Firebug plug-in for Firefox is installed, errors will be displayed in the Firebug console as well. This also includes Firebug Lite which is supported in Internet Explorer 7 and Safari 2.

[edit] Safari console

If Safari debug menu is enabled, errors will be displayed in Safari Javascript console.