Well, I thought I had this issue fixed a really long time ago, but it is now occurring again. Perhaps a fresh set of eyes will help determine the cause and the fix.
This issue occurs on every single project/application I am running, all of which are using SES on ColdBox 2.6.3.
Using SES formatting (yes, I know you’re not suppose to use SES formatting… keep reading):
If I go to an existing handler, but a bad action the invalid event fires perfectly. YAY!
However, if I go to a non-existent handler, the following exception is thrown…
“Could not find the ColdFusion Component or Interface handlers.main/pageNotFound.”
BOO!
Using standard {handler}.{action} formatting:
If I go to *a valid handler, but an invalid action", I get redirected to domain.com/main.pageNotFound, which results in the default view being displayed. BOO!
However, if I go to a non-existent handler, the onInvalidEvent fires properly, displaying the custom 404 message. YAY!
Is anyone else experiencing this? Can anyone see something ridiculously simple that I am overlooking?
Thanks in advance,
Matt