CFCATCH and dynamic custom exception types

By accident someone pointed my on an interesting behaviour of CFCATCH today. It doesn’t seem to be possible to store the names of your own custom exception types in variables and evaluate them in CFCATCH-statements.

That’s not critical at all, because it was quite easy to work around it. I’m not sure what’s the reason for it. It might be that CF generates real java Exception subclasses during the compilation of the template, which aren’t able to handle the dynamic evaluation – but like I said, that’s just a guess.