upgrading from jetty_rails 0.6 into 0.8 broke javascript_include_tag
Reported by Fabio Kung | December 15th, 2008 @ 03:42 PM
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.
Comments and changes to this ticket
-
ps2 December 31st, 2008 @ 02:24 AM
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> -
Tiago Bastos January 20th, 2009 @ 12:31 PM
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.
-
clyfe September 15th, 2009 @ 10:16 AM
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]
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.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Jetty Rails aims to run any Warbler based JRuby on Rails or JRuby Merb applications with Jetty Container, loading configuration from Warbler.
This project is useful for people developing JRuby on Rails (or Merb) applications that can not use mongrel for development. Rails and Merb applications integrated with servlet based applications in the same context would be a reasonable reason.
Fabio Kung
ps2
Tiago Bastos