Migration to ROR

Rails
1

What is the best approach to migrate an application from a technology
(like Java) to Ruby on Rails?

2

Vidya Ramachandren wrote:

What is the best approach to migrate an application from a technology
(like Java) to Ruby on Rails?

Hi Vidya,

You are lucky enough to have Jruby at your rescue.

Learn more about JRuby and you’re the winner all the way.

All you need is Netbeans 6.1 + JVM ( Both free )

Hope this helps.

3

Thanks.
What about migration from other technologies?

Web R. wrote:

Vidya Ramachandren wrote:

What is the best approach to migrate an application from a technology
(like Java) to Ruby on Rails?

Hi Vidya,

You are lucky enough to have Jruby at your rescue.

Learn more about JRuby and you’re the winner all the way.

All you need is Netbeans 6.1 + JVM ( Both free )

Hope this helps.

4

Vidya Ramachandren wrote:

What is the best approach to migrate an application from a technology
(like Java) to Ruby on Rails?

Ask whoever needs the new application what the most important new
feature
is that they need.

Build a view with one button that does that feature. Leave the old
program
online, deploy the new program, and tell your users to open that view to
hit
that button when they need it.

Ask your client what the next feature is that they need. When you add
it,
replicate a little of the old system into the new one. The point is to
phase
out the old system. That pattern is called “strangler fig”. Eventually
the
most common usage of the system will not use the old parts, only the new
parts.

The alternative is this:

Tip: Do not wait 2 years before deploying your app! Deploy it
immediately
and then add features to it.

Write unit tests for everything you do (and port the original tests over

if any!).

–
Phlip
Test Driven Ajax (on Rails) [Book]
“Test Driven Ajax (on Rails)”
assert_xpath, assert_javascript, & assert_ajax

5

Vidya:

Unfortunately the best way is probably to go through some of the
beginning tutorials (I would look for rails 2.0 specific ones if
possible), and then getting the Rails Way as a reference as you begin
to migrate over.

You’ll also want to break down what the current application does, what
models you’d need, controllers etc. Luckily Rails will make it pretty
easy once you get used to it.

On May 3, 2:37 am, Vidya Ramachandren <rails-mailing-l…@andreas-

6

Unless your current site is in an MVC framework already, you basically
have to start from scratch. But, the good news is that you’ve already
got your HTML/CSS which is half the battle.

Here’s my proposed steps:

  1. Sit down and really understand the differences between models,
    views, and controllers – i.e. understanding what each is used for and
    how to determine what code goes in which section
  2. Rethink your current site in an MVC-mindset (don’t try to do this
    while in step 1)
  3. Code your models
  4. Code your controllers
  5. Code your views

On May 3, 3:37 am, Vidya Ramachandren <rails-mailing-l…@andreas-