Refactoring to Rails
This is a project to demonstrate how you might refactor a legacy Java project to use Rails.
The entire repository history is intended to be read start-to-finish. Each commit message is annotated with the goals of that particular step and what to expect. If you simply copy or imitate code from a particular snapshot without understanding how it got there, you're just practicing cargo cult programming :).
We're using the Spring-MVC-based "Petclinic" application as the project subject to the refactoring. We sourced the code of the application from this subversion repository.
There are three versions of the refactoring:
large. Each version is stored on a different branch in this
repository. The three branches build upon each other in succession.
The size name of each of the refactorings is an indicator to the
amount of deviation from the original Java-only Spring MVC project.
The small refactoring is the starting point. We inject JRuby into a specific endpoint in the webapp without disrupting any of the main functionality. A couple of XML endpoints are transferred into Ruby code using Sinatra as the Ruby web framework.
The techniques used in this section could be used to add a RESTful web service wrapper to any existing Java web application.
The medium refactoring introduces Rails into the web application
without restructuring the project. Rails application sources are
src/main/webapp in the place where they would appear in
.war file. The result is that Rails can drive parts
of the webapp but you don't gain the benefits of Rails development
The main technique of note in this refactoring is the use of a "Ruby-first Rack filter": Requests to the application are first handled by Ruby/Rails; if Rails returns an error code, then the request is reset and passed through. This allows Rails to service some requests but leave others alone, so that you can layer successively more Rails requests on top of the existing application.
The large refactoring begins by creating the Rails application structure at the root of the project, and continues by moving more and more functionality from Spring to Rails, until the entire UI layer is ported from Spring MVC to Rails.
The main reason for undertaking a project reorganization is to take advantage of the Rails workflow and tools: the console, generators, profiling and benchmarking, and so on.
The large refactoring is completed by adding Warbler configuration,
coming full-circle back to generating a
.war file of the
application. This shows that you don't have to sacrifice tradidional
Java deployment models while still taking advantage of the "Rails way"
of developing applications.
To play with this code, you should install JRuby, and then
install Bundler with
gem install bundler.
You will also need MySQL installed. You'll need to do the one-time
step of creating the
petclinic database. Assuming the default MySQL
development setup of a root user with no password, run
rake db:create to create the petclinic database. (Alternately, you can log
into the mysql console manually and load the file
At any point in the history, you should be able to:
bundle install: This ensures that you have all the gems needed to run the project.
rake: This runs the test suite. See also the output of
rake -Tto see all available tasks.