Hi Matthew
I think there should definitely be a distinction between exceptions
for non-existent actions (all method names that end in 'Action') and
those that are simply application errors. It will save a lot of
headaches for debugging and help pinpoint both developer mistakes and
also poor programming logic.
(Deposits 2c)
Zend_Controller_Action::__call() exists to provide a mechanism whereby
you can have a default action called when the particular action
doesn't
exist in the controller. By default, it simply throws an exception,
which means the action does not exist.
If you have a typo when doing a method call, it will also be
intercepted
by __call(). Should there be a distinction between exceptions thrown
due
to calls to action methods versus method calls? Possibly. Should you
correct your code if you have an invalid method call. Most likely.
I'll create an issue in the tracker for this, but the main point still
remains: you have an error in your code (which you already know, due
to
the fact that an exception was trapped).
--
Simon Mundy | Director | PEPTOLAB
""" " "" """""" "" "" """"""" " "" """"" " """"" " """""" "" "
202/258 Flinders Lane | Melbourne | Victoria | Australia | 3000
Voice +61 (0) 3 9654 4324 | Mobile 0438 046 061 | Fax +61 (0) 3 9654
4124
http://www.peptolab.com
