Historical errata for Enterprise Recipes with Ruby and Rails

The links on the page footers (at least, for sure on page 208) take me to a page-not-found style page at pragprog.

The “does not only…but also” construct is difficult to read and there are some comma errors. I suggest the following change for simplicity and readability.

FROM: “It does not only support SOAP, but
also its simpler sibling XML-RPC.”

TO: “It supports both SOAP and its simpler sibling, XML-RPC.”

“…That’s a lot of stuff, but most of it is boilerplate…”

Sorry, I don’t buy the premise here. You’ll need to show us how you (easily) generated all of that WSDL from the service we created in the previous example. :)

Not sure if the Big Guy is a Rubyist or not, so I’d suggest “Take Good Care of Your System”. :)

Readability. Suggest changing as follows…

FROM: “Not too long ago applications have been large monolithic blocks that have been linked together from hundreds of object files produced by a C or C compiler.”

TO: “Historically, software applications were built as large monolithic creations, the result of linking together hundreds of individual objects files produced by a compiler.”

The item should be called “Nuts and Gum”, not “Nuts and Gums”.

2nd Paragraph of “What’s In This Book” says:

“Many special tools and techniques are needed to make a software running 99.99999% of the year.”

“Building enterprise software often also means to operate it.”

Perhaps “often also means operating it” ?

Page layout of the text causes the text box to extend beyond footer of page (i.e., truncates off page).

“(sespite” -> “(despite”

Sinara -> Sinatra

The final paragraph refers to the fact that annotate will cause all your models to update on every annotation because of the schema number.
I just downloaded the latest gem version and it doesn’t update all models after a db update. I checked the source code and the annotation code specifically ignores the schema line during the check.

A really great addition would be a quick code sample on how to make annotate part of the rake:migrate task

Introducing the OrderHandler comes as a surprise to me. I use ActiveMessaging in production, and the first thing I thought was, why the heck would I implement a custom handler doing custom work with Stomp, when ActiveMessaging was just introduced to me.

Either some explanation would be in order on why there’s a need for a separate OrderHandler, or move the logic into a processor. Otherwise it doesn’t really add up to me.

And as much as I appreciate XML for what it is, sending YAML inside the messages would make a lot more sense to me. It just feels more Ruby-like.

“install the ruby-opendid gem” should be “install the ruby-openid gem”

In the Users migration, the line

‘User.create(:name => ’maik’, :password => “t0p$ecret”)’

fails. Delete the line.

A sessions view is offered, but the matching changes to the routes.rb file are not made, so these files are not used.

Include the use of “map.resource :session”