From IBM developerworks:
So, should you consider Rails for your next Web application? Well, why shouldn't you? It's a well-written stack of components that work well with each other and are based upon industry accepted enterprise patterns.
[...]
Should you dispense with J2EE altogether in favor of Rails? Absolutely not. J2EE is a well-established standard with several solid implementations and, most importantly, is a proven technology.
- Ruby on Rails and J2EE: Is there room for both?
I spent some time over the weekend advancing my knowledge of Rails and Ruby, and started the working week with "sort out a Maven multiproject build problem" as my first task. After crawling through screenfuls of XML configuration, I'm really starting to appreciate the Rails "convention over configuration" approach.