That is the goal, to be able to run Rails (and all other Ruby
applications) inside JRuby...and by extension on the JVM. There's no
reason Rails couldn't run out-of-the-box on JRuby in a normal
Rails-style deployment, but given that a typical Rails deployment is
CGI-based, it would not make much sense to do the same thing under
Java. Our plan is to get Rails working, first and foremost, and then
find ways to make it work the "Java way" using servlet containers,
jdbc connectors, and application services. This scenario will allow
Rails to run as "Just Another Java WebApp" while still allowing the
agile Rails way of doing things.

The major stumbling blocks currently are the remaining inconsistencies
and incompatibilities in JRuby. As you may be aware, JRuby was
originally written based on Ruby 1.6, and a large part of our efforts
over the last year or two have been to bring it up to
1.8-compatibility. We are nearing this goal, and current efforts focus
on running Rails and other apps, looking for failures or breakage, and
fixing what we find. As a result, we're also getting closer to
functional compatibility with Ruby 1.8 in multiple areas at once. The
day when I can simply run Rails's "generate" script or hit Rails
running in JRuby from my browser is drawing near.

Specific incompatibilities that we're tackling now:

- Poor support for Ruby's socket. Implementing this mainly involves
wrapping Java's Socket, but there are catches here and there.
- Better IO support - we need to swap out java.io code with java.nio
to better support Ruby's IO requirements
- No zlib support - of course this is available in Java, but we still
have to implement the Ruby wrapper
- No continuations - this is the primary reason for the major
refactoring/redesign of the core JRuby interpreter. Already we've
managed to implement bindings, a step toward full continuation support

On 2/16/06, John Wells <[EMAIL PROTECTED]> wrote:
> Just curious...what are the major stumbling blocks to running Rails within
> JRuby? Assuming JRuby intends to be a pure Java implementation of the Ruby
> interpreter, as Jython is for Python, it would seem that the achievement
> of this goal would allow running Rails within a JVM, as opposed to the JVM
> merely serving as a connector.
>
> Thanks,
> John
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Jruby-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jruby-devel
>


--
Charles Oliver Nutter @ headius.blogspot.com
JRuby Developer @ jruby.sourceforge.net
Application Architect @ www.ventera.com


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
Jruby-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jruby-devel

Reply via email to