(I suspect this question has already been answered, but none of my searches have found it).<div><br></div><div>We're moving some of our production Seaside code to VW Seaside 3.0 and I'm tripping over the exception handler. </div>
<div>Q: how do you add a custom exception hander to Seaside in VW?</div><div><br></div><div>In... </div><div> WAWalkbackErrorHandler>>open: </div><div>...the code wraps an exception hander around...</div><div> self session presenter call: (WAWalkback current exception: anException).</div>
<div>...which in VW raises a WAUnhandledNotificationError exception. This is then handed off to the super class to send...</div><div> GRPlatform current openDebuggerOn: anException</div><div>...which opens a debugger on the server (fine for development work). </div>
<div>Selecting 'run' in the debugger will then render the WAVisualWorksWalkback (subclass of WAWalkback) component.</div><div><br></div><div>The exception is raised in... </div><div> WARenderNotification>>defaultAction</div>
<div> <span class="Apple-tab-span" style="white-space:pre"> </span>^ WAUnhandledNotificationError signalWithNotification: self</div><div>...which is not an area of Seaside I spend any time in (and many thanks all those who's work allows me to wallow in ignorance of that code). </div>
<div><br></div><div>In Pharo, the WAUnhandledNotificationError exception is not raised, so adding our own exception hander is trivial. </div><div><br></div><div>I've tested this in VW 7.7 with the latest Seaside loaded...</div>
<div><div> (3.0 - 85,mlucas-smith) </div><div> On: 9/21/10 1:19:37 AM</div><div> 61114: "Port Seaside 3.0 final TO VW 7.8"</div></div><div><br></div><div>Thanks for any help,</div><div>Bob Nemec</div><div>
<br></div><div><br></div><div><br></div><div><br></div>