Web Application Architecture: Principles, Protocols and Practices, 2nd Edition

Chapter 11. Web Application Primer 2: Ruby on Rails

IN THIS CHAPTER

• Comparison of Ruby on Rails with Java EE approaches

• Application requirements

• Administrative interface as a Rails application

• Benefits and drawbacks of using Rails

• Whither Enterprise Java?

OBJECTIVES

• Introduce Ruby on Rails as an alternative to Java EE with Struts/JSTL for web application development.

• Define the requirements for the VRLS administrative interface application to be implemented using Rails.

• Demonstrate the advantages of Rails' rapid application development features (including automated scaffolding).

• Illustrate customization options by improving default page layouts using lookup tables.

• Add pagination, validation, and authentication functionality to the application.

• Show how Rails makes use of inheritance in both application code and reusable page layouts.

• Consider the benefits and drawbacks of using Rails for rapid application development.

• Discuss Rails' readiness as an enterprise application platform.

• Examine Java EE responses to the challenges presented by Rails.

In Chapter 10, we built a VRLS application, implemented as a Java EE application using Struts and JSTL. We also made a strong suggestion that it was not complete without an administrative interface. Without such an interface, seemingly trivial administrative tasks such as adding new listings, resetting customer passwords, and configuring settings for participating realtors would all require intervention by developers or database administrators. In the end, ...