I've read a few posts from the archive regarding the way to handle exceptions occurring in a plugin. In one of them, Matthew W. answers:
What the statement "It is not intended to catch exceptions raised in other plugins or routing" means is that the ErrorHandler plugin can only catch exceptions raised within your action controllers, not exceptions raised in plugins or other areas of responsibility during the dispatch cycle. You can always do your own try/catch blocks and forward as noted above. Is it intentional to not catch in ErrorController the exceptions raised in plugins or is there a hidden technical problem? And, as the way to handle errors is different depending on the place they occur, what is the best practice for application errors? To use in every case a forward to a specific action in the error controller? ----- Guillaume ORIOL Sofware architect Technema -- View this message in context: http://www.nabble.com/what-is-the-best-practice-for-handling-errors-in-application-and-in-a-plugin--tp19527791p19527791.html Sent from the Zend Framework mailing list archive at Nabble.com.
