[Seaside] Seaside 2.9 Debugger

Julian Fitzell jfitzell at gmail.com
Tue Mar 17 18:53:27 UTC 2009

There's an exceptionHandler config option. You'd want to set it to
WAWalkbackErrorHandler to get the 2.8 behaviour but note there is an
issue there currently which is that you won't get a walkback page for
errors that occur while rendering (you'll just get a debugger in the

You can also add a WADevelopmentConfiguration to your app (or to the
Application Defaults configuration) which will set this option (as
well as enable the toolbar) for you automatically. There's still some
work needed on the UI in this area as you can probably tell. :)


On Tue, Mar 17, 2009 at 7:02 PM, John Toohey <jt at parspro.com> wrote:
> Hi,
> I am using the latest 2.9 code and Pharo, and cannot get the SeaSide
> debugger to work. I have added all the WA* libs to my application, but
> I do not see any Halos on my rendered pages, and when I get an error
> in my code, no stacktrace is generated.
> Is there a configuration option that I am missing?
> --
> -JT
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list