Greeting all JRuby & Servlet webelopers, JRuby-Rack 1.1.14 has been released lately, there were no plans to release another 1.1.x but 1.2 is still ahead of us (with a lot of work) so a point release comes handy bringing JRuby-Rack up-to-date esp. since it's been a while bugs got fixed. The 1.1 happens now on https://github.com/jruby/jruby-rack/tree/1.1-stable ... master (towards 1.2.0) might get quite refactored in terms of repo layout. Our latest release provides Rack 1.5 / Rails 4.x compatibility for the servlet session store. We'd also make sure 1.1 still runs fine on Java 6 and JRuby 1.6.x. Also worth noting is that we should better detect "less-common" HTTP method processing such as OPTIONS and not consider default container responses from those as unhandled. Our (configurable) **jruby.rack.error.app** has been fixed and improved - when you're running pooled and run out of runtimes (waiting longer than acquire timeout) it serves a 503.html or 500.html assuming you have one in your /public root. More details on release notes are at https://github.com/jruby/jruby-rack/releases/tag/1.1.14 Happy serving ... make those JavaEE (servlet) containers spin some JRuby :) ! Yours, JR.
on 2014-02-25 07:58
on 2014-02-25 12:13
>Happy serving ... make those JavaEE (servlet) containers spin some JRuby :) ! This reminds me... I was watching a screencast where the presenter said something like "rails doesn't like being in a war file, you have to run it from the filesystem". Can anybody who has experience with deploying rails apps into a container share their experience with me? Happy to chat offline if others are not interested. Cheers.
on 2014-02-25 12:26
Hey Tim, I recommend you try out JRuby-Rack + Warbler yourself instead of listening to advise from a "fare-well" time of what you had to do ... :) Even if someone shared their experience things might be a bit different depending on the container (version) / rails-version / jruby-version. That being said, we've been around for long enough to work decently (+ if your container allows to configure .war expansion be sure to keep it enabled and Rails will break FREE). Happy warbling - deploying, K.