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.
I was questioning the amount of “detective” work needed to find out how cf ticks.
you’re stuck doing something tricky. you’re hoping a small fix using java might help…
– but then your stuck. You’ve got bugger all idea of the api to get CF to call to.
Which java class? What method? how many args?
…
I always thought MACR docs were a bit thin, good for first time but lacking detail and depth – specially compared to the MSDN library…
…but I suppose it’s the thrill of the chase, eh?
“Tally-Ho”
barry.b
Comments on this entry are closed.