You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like isXmlHttpRequest return value may have changed a bit ... from mail sent to Mariano:
Speaking of getting into trouble, I just read the code in WAGemStoneWalkbackErrorHandler>>open: and noticed at the very top these lines:
open: anException
| answer |
self requestContext request isXmlHttpRequest
ifTrue: [ ^ super open: anException ].
and later on in this method there's code that does this:
self session isNil
ifFalse: [
answer := self session presenter
Which is presumably where you get into trouble ... I'm going to guess that for correctly debugging ajax continuations the request needs to answer true to isXmlHttpRequest
...
In frame 22 above the message presenter is not understood, but the sender is not from the context of the WAGemStoneWalkbackErrorHandler so perhaps this is a red herring.
(see the discussion in the mailing list for details](http://forum.world.st/Glass-How-to-remote-debug-exceptions-caused-by-seaside-rendering-td4821668.html)...
Seems that the continuation is
running
instead of opening the debugger...Full stack (in frame 97, the process that should be debugged is showing up):
The text was updated successfully, but these errors were encountered: