Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

upgrading from jetty_rails 0.6 into 0.8 broke javascript_include_tag

#7

from serotonin dude2000@luukku.com, in the jetty-rails mailing list:

I upgraded into jetty_rails 0.8 and after that my javascript_include_tag and stylesheet_include_tag stopped working. I was able to hunt down that someone sets Rails.public_path into RAILS_ROOT/public/public and that's why AssetTagHelper looks into wrong path. I think this must be jetty_rails or jruby_rack issue. Previously I was using jetty_rails 0.6 and didn't have the problem.

Reported by Fabio Kung · December 15th, 2008 @ 03:42 PM

State: new
Milestone: none
Assigned to: Fabio Kung Fabio Kung

Activity

  1. ps2
    ps2

    I believe it's a jruby_rack issue. You can work around it by changing the public.root variable in web.xml to /public/../ Strange hack, but it works for me.

    
    <context-param>
      <param-name>public.root</param-name>
      <param-value>/public/../</param-value>
    </context-param>
    

    December 31st, 2008 @ 02:24 AM

  2. Tiago Bastos
    Tiago Bastos

    I have the same problem, realy looks like a jruby_rack bug:

    If I run a jruby (standalone) script that creates a jetty server using rack, I'm getting the same problem.

    January 20th, 2009 @ 12:31 PM

  3. clyfe
    clyfe

    to fix this edit: jetty-rails0.8.1/lib/jetty_rails/handler/web_app_handler.rb
    on line 11 change
    11 - self.resource_base = @config[:base] + '/public'
    to
    11 - self.resource_base = @config[:base]

    September 15th, 2009 @ 10:16 AM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.