Raf Jaf wrote:
According to my research, I have found nothing to indicate Rails/Ruby
supports native integration with JMS and mainframes.
JMS: not sure. Mainframes: sure, if they expose the proper interface.
DataFabric might also help you.
It was only last week that we looked at Rails for the first time, simply
because we want our client-exposed interfaces to be RESTful.
Rails is not the only RESTful game in town.
Rails is overkill, but do you think Ramaze or Sinatra are better because
they are more lightweight?
Not lightweight so much as modular. Rails generally wants to use AR or
something similar (though this is less true of Rails 3 than Rails 2).
They are still built on Ruby, which puts us
back in the boat: bridging the gap between Ruby and Java.
Easy. JRuby or RJB.
I found this article moments ago which discusses how to implement
ActiveRecord in Java. If I can get this to work in Rails with a custom
Java implementation that hooks into our Java data services, then my
problem is solved.
You shouldn't need to do it that way, if I understand correctly.
Rails is an end-to-end solution. Either use it as one...
I don't agree with this comment. In my experience there is nothing wrong
with using special aspects of one framework alongside other
In this case, you are wrong. Rails is a full-stack framework. If
you're not going to use most of the stack, there is no point in
incurring the extra overhead of using it in your project.
Anyway, thanks for the info.