Kevin Dangoor wrote:
I'm inclined to say that if there's no @error_handler() declaration and no tg_errors, the validation exception is raised (not counting the legacy validation_error method, which will die soon enough). It's ugly for such a thing to get through to users, but it's *so* easy to define the error behavior that it seems better to just hand the exception back up the chain.
Done (r701). NotImplementedError is raised along with an explanation.
You should be able to call another method directly, if that's all you're looking to do. I've done it in the past...
I know. But it does not embrace REST. Simon
