The default setting of the framework is to store all exceptions in the
response object, if you do a
 
  $front->throwException(true);

the exceptions get thrown. Your error message "Invalid controller
specified(error)" tells you that there is no ErrorController.php. If you
use the defaults there is an ErrorHandler Plugin that catches the
exception and forward them to this controller as described in the manual:

http://framework.zend.com/manual/en/zend.controller.plugins.html#zend.controller.plugins.standard

Take a look at the manual of the response object to see the different
methods of the response object that work with exceptions
($response->setException(), $response->hasException() , ...)

best regards,
Truppe Steven

Philip G wrote:
>
> Okay, how do I decrypt this?
>
> It would seem when anything goes wrong, I get a
> "'Zend_Controller_Dispatcher_Exception' with message 'Invalid
> controller specified (error)'" Error message. It's extremely generic.
> Let see, I got it when controller name/file/class was mistyped; when a
> view file didn't exist; when Zend_Auth_Adapter_DbTable failed to run.
> Who knows how many more errors I'll run into.
>
> After much deliberation, I found out that Controller class seems to be
> catching the exception itself and throwing out a generic message. I
> don't like this...
>
> Is there anyway to force the Controller to throw back the original
> exception? Constantly getting the above exception makes it extremely
> hard to pin-point exactly where the error is occurring.
>
> Cheers
>
> -- 
> Philip
> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
> http://www.gpcentre.net/ 

Reply via email to