<div class="gmail_quote"><div>Evidently, that's just the way it is (we opened a case with Cincom, 424170). Exception handling is handled well by WebVelocity but that code will not be ported to their Seaside implementation. Unless I'm missing something, subclassing <span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">WAExceptionHandler in VW is of little use since </span><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">WAUnhandledNotificationError will be raised when the exception handler is called, and that opens a debugger on the server. </span></div>
<div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><br></span></div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">It's easy to see the difference between Pharo and VW using something like... </span></div>
<div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><br></span></div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><div>
renderContentOn: html</div><div> html form: [</div><div> html button</div><div> callback: [self error: 'This is only a test'];</div><div> with: 'Press for error']</div>
<div><br></div><div><div>In VW, this opens a debugger on the server. If you then press 'run' you'll see a stack trace on the browser.</div><div>In Pharo, this renders a stack trace on the browser, and if you press 'debug' it opens a debugger on the server.</div>
</div><div><br></div><div>I'd love to know how others have worked around this.</div><div>Thanks,</div><div>Bob</div></span></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<...></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">It sounds like you are not in a render phase when hitting your error,<br>
though, since a WARenderNotification is being signaled. Signaling that<br>
notification is completely normal and happens at the end of more or<br>
less any action phase to indicate that a new render pass should begin.<br>
This is normally caught by<br>
WARenderLoopContinuation>>withNotificationHandlerDo: so the question<br>
is, why is the VW implementation not doing so?<br>
<br>
Michael may be able to shed some light or maybe you can determine more<br>
by looking further up your context chain...<br>
<br>
Julian<br>
_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
</blockquote></div><br>