Just about every convention in Rails can be overridden, so in theory you can always adapt to a legacy schema.
Having said that, there are times where this might get to be just too much of a pain. My advice would be to experiment with writing basic models that map any legacy schema you might be thinking of using, and seeing if it works, before comitting to the full application.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Agile Web Development with Rails: conventions & legacy systems