JRuby

ClassCastException when using include of java interface on ruby class that that inherits from Hash

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: JRuby 1.5, JRuby 1.5.1
  • Fix Version/s: None
  • Component/s: Java Integration
  • Labels:
    None
  • Testcase included:
    yes
  • Number of attachments :
    1

Description

When you include a java interface on a class that inherits from Hash you get a ClassCastException: "cannot be cast to org.jruby.RubyHash" when creating a new instance.

The problem only occurs when the class inherits from a class that itself inherits from Hash like OrderedHash in ActiveSupport. If you inherit directly from Hash there is no problem.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Brian Olsen added a comment -

Simplified the test and uploaded it as a gist: http://gist.github.com/430092

Show
Brian Olsen added a comment - Simplified the test and uploaded it as a gist: http://gist.github.com/430092
Hide
Permalink
Douglas Campos added a comment -

the problem still exists on |jruby 1.6.0.dev (ruby 1.8.7 patchlevel 249) (2010-10-30 cefd8e9) (Java HotSpot(TM) 64-Bit Server VM 1.6.0_20) [darwin-x86_64-java]|

added stack trace here => http://gist.github.com/659137

Show
Douglas Campos added a comment - the problem still exists on |jruby 1.6.0.dev (ruby 1.8.7 patchlevel 249) (2010-10-30 cefd8e9) (Java HotSpot(TM) 64-Bit Server VM 1.6.0_20) [darwin-x86_64-java] | added stack trace here => http://gist.github.com/659137
Hide
Permalink
Charles Oliver Nutter added a comment -

Ok, I think the problem here is that when extending Hash directly, the class generation logic recognizes that the superclass is Hash and its generated Java class needs to extend RubyHash. In the OrderedHash case, the superclass has not been "reified" into a real class yet, so the subclass just extends RubyObject, and as a result can't be called with RubyHash methods.

There's a task still in the queue to unify the reification logic and the runtime implementation/extension logic. Until that's done I think trying to fix this would be mostly academic.

Show
Charles Oliver Nutter added a comment - Ok, I think the problem here is that when extending Hash directly, the class generation logic recognizes that the superclass is Hash and its generated Java class needs to extend RubyHash. In the OrderedHash case, the superclass has not been "reified" into a real class yet, so the subclass just extends RubyObject, and as a result can't be called with RubyHash methods. There's a task still in the queue to unify the reification logic and the runtime implementation/extension logic. Until that's done I think trying to fix this would be mostly academic.

People

  • Assignee:
    Unassigned
    Reporter:
    Brian Olsen
Vote (0)
Watch (1)

Dates

  • Created:
    Updated: