Forum: JRuby JRuby-rack and Rails 3.0.0.beta?

I've recently upgraded a Rails 2.3.5 app to Rails 3, and while the 
built-in
Webrick server works just fine, I'm a bit stuck with jruby-rack. I can 
see
that it's starting Rails, because a warning about 'class_eval' (known 
issue)
pops up on stderr, and Jetty itself takes an appropriate amount of time 
to
start, but any page access results in the default Rails error page.

The odd thing is, Rails doesn't create a logfile, and the Jetty logs 
don't
show any errors either.

So, before I go too nuts, has anybody gotten the Rails 3 beta working 
with
Jetty/JRuby-rack, and if so, anything I might be missing?

I think this has been mentioned in other replies, but jruby-rack
and/or warbler do not (yet) support Rails 3. It's coming :) Maybe you
can help?

On Fri, Feb 19, 2010 at 7:39 PM, Don Werve <donw@madwombat.com> wrote:
> I've recently upgraded a Rails 2.3.5 app to Rails 3, and while the built-in
> Webrick server works just fine, I'm a bit stuck with jruby-rack. I can see
> that it's starting Rails, because a warning about 'class_eval' (known issue)
> pops up on stderr, and Jetty itself takes an appropriate amount of time to
> start, but any page access results in the default Rails error page.
> The odd thing is, Rails doesn't create a logfile, and the Jetty logs don't
> show any errors either.
> So, before I go too nuts, has anybody gotten the Rails 3 beta working with
> Jetty/JRuby-rack, and if so, anything I might be missing?

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

IS there a list of "things" that need to be done to support Rails 3?
I'm currently playing with some code to support Async requests through
Rack and I'm building some pseudo jruby-rack code to a) learn what
jruby-rack is doing (I'm also looking at Torque box's jruby-rack code
as well).  I was thinking of playing with Rails 3.

If there is no list... is it just a matter of running tests and
looking at bugs?

Jay

On Tue, Mar 2, 2010 at 2:40 PM, Charles Oliver Nutter
<headius@headius.com> wrote:
>> The odd thing is, Rails doesn't create a logfile, and the Jetty logs don't
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

On Fri, Feb 19, 2010 at 7:39 PM, Don Werve <donw@madwombat.com> wrote:
> I've recently upgraded a Rails 2.3.5 app to Rails 3, and while the built-in
> Webrick server works just fine, I'm a bit stuck with jruby-rack. I can see
> that it's starting Rails, because a warning about 'class_eval' (known issue)
> pops up on stderr, and Jetty itself takes an appropriate amount of time to
> start, but any page access results in the default Rails error page.
> The odd thing is, Rails doesn't create a logfile, and the Jetty logs don't
> show any errors either.
> So, before I go too nuts, has anybody gotten the Rails 3 beta working with
> Jetty/JRuby-rack, and if so, anything I might be missing?

The main issues I'm aware of are just getting Warbler and JRuby-Rack
to be Bundler-friendly -- it's work in progress as Charlie said :). If
you can manage to get all the gems and libraries into a war file,
Rails 3 should work as a vanilla Rack application at least.

/Nick

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

That's actually what I ended up doing night before last, and it works 
just
fine!

once I have everything in war file - gems + jars, what do I need to do
to tell rails to use these gems ? set ENV['GEM_HOME'] +
ENV['GEM_PATH'] ? sorry if I did not see the obvious !!

thanx Kristian

On Thu, Mar 4, 2010 at 9:39 AM, Don Werve <donw@madwombat.com> wrote:
> That's actually what I ended up doing night before last, and it works just
> fine!
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email