InfoQ

News

Follow the Progress of JRuby on Rails

Posted by Obie Fernandez on Nov 28, 2006 11:17 AM

Community
Ruby
Topics
JRuby
Tags
Testing ,
Rails

Charles Nutter has been keeping an updated page of Rails test run results that shows progress towards the goal of a fully-functioning JRuby on Rails. Members of the JRuby team have already demonstrated Rails applications working on JRuby, and even ActiveRecord talking to databases via JDBC. To be clear, what we're talking about here is the effort to get the sizable Rails test suite running at 100% passing.

According to Charles' recent comments to the rails-core mailing list, Rails components ActionPack, ActiveSupport, and ActionMailer are nearly 100%. Other parts of Rails still have some work left:

ActiveRecord is probably 2/3 working (but the failures include tests for Oracle, PgSql, Firebird...), and most of what we'd expect to work in Railties works pretty well. I haven't primed the pump to run ActionWebService tests yet.

The JRuby team has been targeting Rails 1.1.6 support, but will begin testing Rails 1.2 soon:

I wouldn't imagine the compatibility profile will change that much by switching versions; we're mostly talking about pure Ruby here. Note that the use of SQLite in many places in the test causes quite a bit of trouble for JRuby since SQLite support on Java is minimal at best. The ability to swap out SQLite for something equivalently simple (DBI or JDBC with Derby/JavaDB, perhaps?) would make it easy to run those tests.

Charles and the JRuby team are still looking for additional help with this worthy effort:

Of course, if any of you are Java devs and would like to help us get things running, we'd certainly appreciate it. I've debugged and traced through enough Rails code to know that having more expert folks contributing would really help.

1 comment

Reply

contributing by Alex Popescu Posted Nov 28, 2006 5:12 PM
  1. Back to top

    contributing

    Nov 28, 2006 5:12 PM by Alex Popescu

    I would definitely like to hear what are the fields JRuby needs help. I have always thought that oss projects clearly stating their needs will have better chances to find their resources (and I am not talking about the always recommended approach: get involved in the ml, submit bugs, submit patches for the bugs, etc.).

    ./alex
    --
    :Architect of InfoQ.com:
    .w( the_mindstorm )p.
    Co-founder of InfoQ.com

Exclusive Content

Diary of a Fence Sitting SOA Geek

In this presentation, Mark Little explains the history of SOAP/WSDL/WS-*-based web services and RESTful HTTP and highlights how the two approaches might converge into a single solution.

Flex for XML and JSON

Platforms need interoperability. In this article Flex interoperability with JSON and XML is explored including direct mapping to chart and grid components.

Measuring Agile in the Enterprise: 5 Success Factors for Large-Scale Agile Adoption

Michael Mah analyzes the development process in 5 companies: 2 Agile (one of them BMC) and 3 classic. He presents the factors which contributed to the success of BMC's Agile adoption.

Tom Preston-Werner on Powerset, GitHub, Ruby and Erlang

In this interview filmed at RubyFringe 2008, Tom Preston-Werner talks about how both Powerset and GitHub use Ruby and Erlang, as well as tools like Fuzed, god, and more.

David Laribee on Alt.NET and its Mission

David Laribee discusses the purpose of ALT.NET, its mission and future.

Discover RailsKits and Stop Writing Redundant Code

Ruby on Rails has become a popular Ruby framework for creating web applications in recent years. An aspect of creating a web application is the need to repeatedly create the same base functionality.

A Formal Performance Tuning Methodology: Wait-Based Tuning

Steven Haines talks about tackling web application performance tuning by proposing a method called wait-based tuning.

Shaw and Fowler About Forging a New Alliance

Shaw and Fowler talk about the need for a new relationship between the business department and the IT department. Studies have shown that projects mostly fail due to miscommunication between the two.