Errata for Rails for Java Developers

#29375: When running 'ruby script/console', I got the following error:

./script/../config/boot.rb:43:Warning: require_gem is obsolete. Use gem instead

When I changed that boot.rb file accordingly, the warning was no longer there--David

#28958: The class TestPrimitives does not compile, because in the method, on line 1.:

0. public void testSomeLegalConversions() {
1. assertEquals(2.1, 2 + 0.1);
2. assertEquals("B12", "B" + 12);
3. }

The method assertEquals(double, double) does not exist.--Gian Franco

#30320: The "Rails App in Fifteen Minutes" section fails badly with Rails 2.0. I discovered the change in database configuration, and was able to change it to point to a MySQL server (unnecessarily). If you progress that far, once browsing to localhost:3000/people, you get a 404 page:

Routing Error

No route matches "/people" with {:method=>:get}

An associate directed me to downgrade Rails to version 1.2 to continue a match with the book.--Morris Jones

#30381: The sample scaffold app "people" doesn't successfully execute tests with a rake command in rails 1.2.6. It generates eight errors as follows:

StandardError: No fixture with name 'first' found for table 'people'

I don't know the solution. :(--Morris Jones

#28534: When executing "script/console" the error occurs on macosx 10.4 (maybe should be mentioned how to solve).

=> Booting WEBrick...
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/routing.rb:965:in `build': Illegal route: the :controller must be specified! (ArgumentError)
from /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/routing.rb:1172:in `add_route'
from /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/routing.rb:986:in `connect'
from ./script/../config/../config/routes.rb:27
from ./script/../config/../vendor/plugins/selenium_on_rails/switch_environment/init.rb:19:in `draw'
from /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/routing.rb:1139:in `draw_without_selenium_routes'
from ./script/../config/../vendor/plugins/selenium_on_rails/switch_environment/init.rb:15:in `draw'
from ./script/../config/../config/routes.rb:6
from /usr/local/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/active_support/dependencies.rb:488:in `load'
... 19 levels...
from /usr/local/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/active_support/dependencies.rb:495:in `require'
from /usr/local/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/active_support/dependencies.rb:342:in `new_constants_in'
from /usr/local/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/active_support/dependencies.rb:495:in `require'
from script/server:3

#26953: The code from code/rails_xt/samples/programmer.rb (dated 11/28/06) doesn't run because it's missing the following at the top of the source code:

require 'person'--Eli

#27951: Tried the 'rake migrate' and rake 'db:migrate' as well, but getting the same error:
"Illegal route: the :controller must be specified!"

Any idea what to do with this missing controller?

cadima@mac.com--Dmitry Shultz

#27024: To fix the error listed at #6143, just change the line
map.connect 'people/:action/:full_name'
to
map.connect 'people/:action/:full_name', :controller=>'people'

#26896: When running the rake command using Rail 1.2.1 you get the following message:
Illegal route: the :controller must be specified! (ArgumentError)

They change the RouteBuilder--Jerry Hoerig

#27783: I am still having problems with the rake migrate. I added to map.connect
'people/:action/:full_name', :controller=>'people'
Now it is indicating "Bad file descriptor - connect(2)"
I did a --trace but there were not enough details to determine what command was executing when the error occured.
Ray Hooker
rhooker@cisco.com--Ray Hooker

#29261: The download link does not work.
Also, the routing code on page 135 DOES NOT CONTAIN the code that is described in the surrounding text.

Take pity on us bleating of a Rails noob!

- Jason Ziegler

PS: I LOVE this error-reporting interface and especially its integration into the PDF. Thank you!--Jason Ziegler

#50313: Whoa Not MailChimp April 6th, 2009 3:35 am Shame you choose to hihglight MailChimp. People might think they're a legitimate business. Been spammed out the wazoo from clients of theirs, no end in site. Unsubscribe? Might as well call it subscribe me ten times over'. Their abuse pages are usually broken, and their complaint page requires you to pluck some obscure value from the url embedded in the email header. Good luck finding that, Grandma. Gotcha, and you'll never leave!--peaepOXNBXlUOQ