Yeah thats where I had to go looking as well for the actual error, strange that Railo can display it right… Well maybe not strange, it is Adobe after all 
Well, I’ve found Adobe and Railo both have quirks. This bug in particular makes debugging issues with our Railo Couchbase extension a lot harder:
https://issues.jboss.org/browse/RAILO-2517
Thanks!
~Brad
ColdBox Platform Evangelist
Ortus Solutions, Corp
E-mail: brad@coldbox.org
ColdBox Platform: http://www.coldbox.org
Blog: http://www.codersrevolution.com
Yeah, I think this is an Adobe CF and Railo difference. The “type” of the Java exception that gets thrown from the Couchbase libraries is "com.couchbase.client.protocol.views.InvalidViewException’
Railo will allow me to catch that specifically with this:
catch(‘com.couchbase.client.protocol.views.InvalidViewException’ e) {}
But Adobe CF won’t do it. The official docs on cfcatch say:
The custom_type type is a developer-defined type specified in a tag. If you define a custom type as a series of strings concatenated by periods (for example,), ColdFusion can catch the custom type by its character pattern. ColdFusion searches for a tag in the block with a matching exception type, starting with the most specific (the entire string), and ending with the least specific.
I think I may put in a ticket for this since it’s a darn useful feature and Railo seems to work. I’ve been on Adobe CF, but with the same Couchbase server and since I tested on Railo first, the view had already been created so the error was never being thrown for me.
I think for now I’ll have to change the library to catch “any” like you did.
Thanks!
~Brad
ColdBox Platform Evangelist
Ortus Solutions, Corp
E-mail: brad@coldbox.org
ColdBox Platform: http://www.coldbox.org
Blog: http://www.codersrevolution.com
I have to agree, many times I have tried to do that myself… So if there is a bug # I will vote for it as well.