Benefits of Rails without ActiveRecord, Grails without GORM
We have several large web applications written in a variety of versions of Struts and Tapestry; we're not particularly happy with any of those web app frameworks and we're looking to pick a new one for development of future applications.

The kicker is that we still want the new stuff to leverage our existing data, which is basically SOAP web services backed by Hibernate -- we don't want to rewrite any of that.

My limited experience with Rails suggests that a lot of the benefit comes from the integration of ActiveRecord, and I'm guessing that Grails/GORM is a similar situation. I'm wondering, what are the other major benefits of Rails and Rails-like frameworks? What are the reasons you would choose a Rails-like framework if you weren't going to get to use its ORM system, and what are the reasons you wouldn't?

[Yes, this is probably community wiki. :)]
Benefits of Rails without ActiveRecord, Grails without GORM
===

We have several large web applications written in a variety of versions of Struts and Tapestry; we're not particularly happy with any of those web app frameworks and we're looking to pick a new one for development of future applications.

The kicker is that we still want the new stuff to leverage our existing data, which is basically SOAP web services backed by Hibernate -- we don't want to rewrite any of that.

My limited experience with Rails suggests that a lot of the benefit comes from the integration of ActiveRecord, and I'm guessing that Grails/GORM is a similar situation. I'm wondering, what are the other major benefits of Rails and Rails-like frameworks? What are the reasons you would choose a Rails-like framework if you weren't going to get to use its ORM system, and what are the reasons you wouldn't?

[Yes, this is probably community wiki. :)]