[Catalyst] Error handling strategy wrt /end

[Phil Mitchell]

My actions all have an eval block that lets me catch and handle exceptions
thrown by my model classes. What this leaves out is any exceptions that
arise once the work is handed off to the TT view -- in /end. What this means
is that for most errors, I provide a nice error message; but if TT dies, the
user gets the generic catalyst error screen. Not nice.

I could catch these exceptions by explicitly forwarding to /end inside each
eval cage, but that kind of defeats the point of having the /end action.
Also, I don't want to use TT try/catch blocks, bc I want the error handling
all in one place.

Curious to know how other people approach error handling.



--
==========================
2People Blog: http://2-people.blogspot.com/
2People site: http://www.2people.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rawmode.org/pipermail/catalyst/attachments/20060126/3b67c86a/attachment.htm