Deprecated: The each() function is deprecated. This message will be suppressed on further calls in /home/zhenxiangba/zhenxiangba.com/public_html/phproxy-improved-master/index.php on line 456
InfoQ: JRuby 0.9 Released; Runs WEBrick, Rails, RubyGems, and Rake
[go: Go Back, main page]

InfoQ

News

JRuby 0.9 Released; Runs WEBrick, Rails, RubyGems, and Rake

Posted by Floyd Marinescu on Jul 05, 2006 10:14 AM

Community
Ruby,
Java
Topics
Web Frameworks,
Ruby on Rails
Released today, JRuby 0.9 can now run RubyGems, the WEBrick Ruby HTTP server, and Ruby on Rails (on WEBrick).  JRuby co-lead Thomas Enebo told InfoQ that Rake also recently started to work.  JRuby 0.9 also includes a number of bug fixes, an improved YAML parser thanks to JvYAML and RbYAML projects, and all non-native standard libraries are bundled in the JRuby distribution.

JRuby is a Ruby 1.8.2 compatible Ruby interpreter written in Java. It supports most built-in Ruby classes and also supports  interacting with and defining java classes from within ruby. JRuby is seen by many in the Ruby community as a way to take Ruby and Rails mainstream with first class deployment support (the JVM) and strong integration with Java.   In the Java community, some see it as the answer to improving web development productivity while still staying on the Java platform and preserving existing investments in Java.

InfoQ spoke briefly to project co-lead Thomas Enebo who mentioned "The applications we spent a lot of effort on were Ruby on Rails,WEBrick, and RubyGems. Recently we noticed Rake started working as well. These four are all important applications in the Ruby world.  If you look at the complexity of Rails by itself, then you can get some appreciation of the above quoted statement.  We think most standard (non-native) libraries are working, but need users pounding on them to tell us whether that is true or not.  We still know of problems and missing methods, but it feels like we turned a corner on JRuby's correctness as a Ruby interpreter."

On when 0.9.1 is coming out and what to expect, Thomas told InfoQ:
 We want to have another release near the end of this summer (end of August).  We made a promise at JavaOne that we would completely support Ruby on Rails and we want to:
1. Fix more incompatabilities so Rails runs better.
2. Speed up JRuby to make it more attractive as a Rails environment
3. Provide a JEE-backed deployment option for Rails.  This will start  with a servlet acting like a fast-CGI.
Tags
JRuby

2 comments

Reply

congrats by graham o'regan Posted Jul 6, 2006 2:35 PM
Excellent... Excited about JDBC and Ruby! by Eric Kramer Posted Jul 18, 2006 11:29 AM
  1. Back to top

    congrats

    Jul 6, 2006 2:35 PM by graham o'regan

    I think this is great news. I've been writing Java apps for years and have recently started looking at RoR for a few small applications (in-house and external) and it's nice to get that productivity shot-in-the-arm for crud apps at the very least. I've held back on doing too much in the past because I found that I missed a lot of the functionality that I'm accustomed to in Java, but I'll definitely be investigating this further.

  2. Back to top

    Excellent... Excited about JDBC and Ruby!

    Jul 18, 2006 11:29 AM by Eric Kramer

    Over the past year I've fallen in love with Ruby. While I haven't done much with Rails yet, I've fallen in love with the Ruby Way. One thing that has always seemed problematic was the very "native" approach used for the Ruby database integration (typically achieved via the 'DBI' library and associated 'DBD' drivers). While vendors are very likely to produce JDBC drivers for their databases, I'm unaware of any "big players" (Oracle, SQL*Server, Informix, DB2, Cache, Sybase, etc.) providing direct Ruby DBI/DBD support. While ODBC helped a bit here, I found getting ODBC (and drivers) to work on non-Windows platforms to be less than trivial.

    With the advent of JRuby, we have the option of using the JDBC API to access virtually any database platform. I think it would be very beneficial if the JRuby project came up with some sort of transparent DBD-to-JDBC driver that would allow Ruby code to transparently use any JDBC driver just like a "regular" DBI/DBD driver.

    Congratulations everyone... This is a very exciting development!!

Exclusive Content

Leading From A Position Of No Power: A Customer’s Perspective of an Agile Team

Last year Agile coach Alexia Bowers walked a mile in a project customer's shoes, and told us at Agile2006 how it felt. She stressed the need to strive for creativity instead of cutting scope.

Interview: IBM Architect Bertrand Portier on joining MDD and SOA

In the wake of the latest product announcement from IBM, InfoQ talked to Bertrand Portier about a RedBook that presents a fairly general Model-Driven-Development approach to service construction.

Joe Walker on DWR

InfoQ spoke with Joe Walker at QCon London 2007 about the DWR toolkit. Walker discussed DWR 2.0, new features like 'reverse AJAX', the TIBCO deal, Spring integration, and applications of DWR.

Prototype and Script.aculo.us: spending weekends at home again

Script.aculo.us creator Thomas Fuchs gives an overview of the concepts and functionality of both Prototype and the script.aculo.us libraries.

Jeff Sutherland on Scrum and Not-Scrum

Dr. Jeff Sutherland guesses there are 120,000 standup meetings held daily worldwide. He uses "the Nokia test" to distinguish between "doing Scrum" and simply using an iterative process.

Jay Fields and Zak Tamsen on Domain Specific Languages

Jay Fields and Zak Tamsen talk with InfoQ about how they use Domain Specific Languages to deliver business value to their projects at ThoughtWorks.

Erik Doernenburg on Software Visualization

Erik Doernenburg talks with InfoQ about different software visualization strategies using a combination of free tools and custom development.

Setting out for Service Component Architecture

Henning Blohm, Java EE Software Architect at SAP and Co-Chair of the SCA-J Technical Committee provides his perspective on SCA as a cross-technology programming model integration.