getting object log continuation for rest api calls

I have a REST handler using Seaside-REST. I like to have to same behaviour as in web applications. If an error/exception occurs than a continuation should be stored in the object log for later debugging. I tried a lot but I cannot figure it out.
As far as I understand it this should work out of the box. If I register a handler there is a WAExceptionFilter added automatically. And this uses WARemoteDebuggingWalkbackErrorhandler. But it just does not work.

Any hints?

Norbert

Norbert,

I'll have to dig into this one a bit as whether the WAExceptionFilter
works out of the box or not dependes upon where the REST handler splices
itself into the stack ... I think that the REST handler splices in above
the WASession code, so I imagine that the error handlers are installed
along with the session ... I have to check to be sure, but given that
you're having trouble, I would assume that that's true ...

I have been threatening to add a continuation-based exception handler
near the top of the stack ... inside the adaptor layer ... since getting
error stacks at all levels would be quite useful so this issue may just
be the motivation I need to go ahead and do that:)

Dale

On 11/22/2010 10:36 AM, Norbert Hartl wrote:
> I have a REST handler using Seaside-REST. I like to have to same behaviour as in web applications. If an error/exception occurs than a continuation should be stored in the object log for later debugging. I tried a lot but I cannot figure it out.
> As far as I understand it this should work out of the box. If I register a handler there is a WAExceptionFilter added automatically. And this uses WARemoteDebuggingWalkbackErrorhandler. But it just does not work.
>
> Any hints?
>
> Norbert
>