I was just working with the Twitter4J library (Java) this week. It throws a Twitter.4J.exception object that really jacked up my pages if I didn’t catch it and re-throw it as a CF error. (Somehow it actually caused the HTTP headers to be incorrectly terminated in the server’s response.) I had to test the type of exception and decide if it came from CF or not. What’s weird, is I think I tested it with exception.type (from a suggestion on a Mark Mandel blog) even though if I dumped the exception it showed up as a straight java object with no “type” propery.
~Brad