Closed CSchulz closed 11 years ago
I think this is an issue with JRuby 1.6.8 - you do need to "unwrap" rescue-d Java exceptions ... (try using getCause). This is "fixed" in 1.7 ... also next time you report please make sure you're using the latest JRuby-Rack. There are several ways you can ask about issues you're unsure ... check http://jruby.org/community
getCause isn't available, too. But I found out that you can use the exception object like a "normal" string. It shows only the message nothing more.
Hello,
I have made the experience the last days that there is something wrong with the exception handling. It seems that is something going wrong internally. I hope I am right here, I don't where to ask.
I am fetching the class with JRuby and use rescue to catch the exception. I can't use any of my methods, only backtrace from the NativeException is possible.
That is the point I don't understand, I fetch the class descriptor give it to the rescue and expect the object of the exception caught.
In some cases it works, but it wasn't possible yet to find out, what the difference is.
The log says following (jruby-complete-1.6-8 and jruby-rack-1.1.10):
With jruby-complete-1.7.3 and jruby-rack-1.1.13.1 I got following message: