-
-
Notifications
You must be signed in to change notification settings - Fork 920
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
undefined method `__ruby_object' for interface implementation #1184
Comments
Comment by @donv: Calls to hasCode, equals, and __ruby_object are being forwarded to the Ruby class, while I think they should be handled by the proxy. Comment by @headius: Ok...looks like the logic involved with defining __ruby_object does so to have a reference to the real "self" that goes with a proxy type, and the call that fails is coming from JavaUtils.trySimpleConversions attempting to call that method. Comment by @donv Thanks for looking into this. |
I think I have found the problem, and I have at least one part of the solution. In org.jruby.javasupport.Java lines starting at 1207 "==" is used to test for methodName. Changing this to ".equals" fixes the immediate problem. I addition to this, I think the "WTF" is right. We should call toString, hashCode and equals on the Ruby object, not the class. I can change it if you agree. |
…ntation * Use #equals instead of == to compare the method name String objects since == will return false if the String objects have the same content, but are different instances.
Original bug: https://jira.codehaus.org/browse/JRUBY-7150
Filed by @donv
I could use some help in figuring this out. Any help is greatly appreciated.
When unregistering a previously registered LocationListener we get the exception listed below. The code for the application is in the Ruboto GPS tutorial: https://github.com/ruboto/ruboto/wiki/Tutorial%3A-get-current-gps-position
I am not sure wether this is a regression or not. The example was originally written a long time ago, and I think it worked fine then :)
The text was updated successfully, but these errors were encountered: