Takai has posted a brief howto on running RoR apps in Glassfish, which Charles and half the free world is linking to. Since I seem to have been in a run of profoundly negative discussions around here lately anyway, allow me to get all Jay Sherman on this one too:
Yeah, running Rails apps in JEE servers is cool, and it has the possibility to really open up a new world for Rails, but this seems to be sidestepping one of the things I most wanted to see. Let’s look at the instructions.
1. Copy follow files to
3. create config file to
4. generate rails app to
Seems to me #1 should be optional and the rest of it should be:
WAR packaging is one of the things JEE has going for it in a big way. I know Tim has talked about PHP and Ruby vs Java at the language level, but he and everyone else on the planet will generally concede that the tooling for Java is second to none, and this seems like part of that. However, anyone who remembers what deployment of webapps was like back in the day, or people who still juggle tgz’s of their apps around between servers for PHP or RoR absolutely adore the simplicity of WAR based deployment. Having Grizzly simply redirect requests to Rails isn’t even on the list of things I would have worried about at this point in the game, and leaving me with another directory structure/non-remote based deployment doesn’t seem like progress.
This was the impression I got as a target for JRuby from the get go, and while I understand it might be slower — come on, if we cared a whole lot about slow at this point, would we really be talking about Ruby at all? :P — just having a template Servlet that can send off requests to the JRoR environment seems like a much better option here.
This concludes this Andy Rooney moment.