Handling remoting exceptions

[andrew.rw.robinson]

I am curious on the recommended way to handle errors in the Seam remoting calls.

Since Java doesn't have multiple return value support it is hard to return one type of data (like an int) and also return error information to show to the user.

I could develop some kind of special return value that is easy to parse in JavaScript, but that doesn't seem like a good API at all.

I tried throwing a Java exception to see if the Seam code could handle it, but I got a null JavaScript exception in the process response code.

What are other people doing? Is there better support for this in 1.1 over 1.0?

Thanks,
Andrew

[andrew.rw.robinson]

I ended up creating a special return class that can hold a value as well as return an exception to the client caller, but I would be nice to be able to have this automatically wrapped. I tried a custom annotation and interceptor on my @WebRemote method that would catch exceptions and change the return type to my custom object, but my interceptor was never called.

[andrew.rw.robinson]

One more question,

Do @Render/@Redirect work with Seam remoting @WebRemote methods, so that the page can be redirected to a new view if the @WebRemote method fails with an exception?

[gavin.king]

No.