There are three error handlers that you should be using with GLASS:

1. WAWalkbackErrorHandler
2. WARemoteDebuggingWalkbackErrorHandler
3. WAGemStoneProductionErrorHandler

WAWalkbackErrorHandler

The WAWalkbackErrorHandler brings up a Seaside Walkback page that looks like the following:

If you click on the Debug link, a hard break will be triggered.

If the Seaside server was launched from a GemTools image when the hard break is triggered, then a debugger window will open.

If the Seaside server was run from a topaz session, then the topaz process will exit with an error. You should use the WAGemStoneProductionErrorHandler instead.

WARemoteDebuggingWalkbackErrorHandler

The WARemoteDebuggingWalkbackErrorHandler brings up a Seaside Walkback page that looks like the following:

If you click on the Debug link, a continuation is snapped off and added to the ObjectLog. You can bring the debugger up on a continuation in the ObjectLog by using the Debug menu in GemTools.

Use WARemoteDebuggingWalkbackErrorHandler when you are doing development and have launched the Seaside gems in separate topaz processes.

WAGemStoneProductionErrorHandler

When an exception is hit while using the WAGemStoneProductionErrorHandler a page that looks like the following is displayed:

A continuation is automatically added to the ObjectLog and like the WARemoteDebuggingWalkbackErrorHandler, the continuation can be debugged in GemTools.

The WAGemStoneProductionErrorHandler is intended to be used in production, when you don't want your uses to be confronted with a Smalltalk walkback window.

The page that is displayed by WAGemStoneProductionErrorHandler can be customized.