11 comments

• 

  student1

  7 months ago

  Could you show us JRuby ?
  
  When the class is over, could we still access these screen casts ?
  
  Thanks
  reply
• 

  xertroyt

  6 months ago

  I will leave the screencasts up unless my bandwidth bill increases!
  
  JRuby is a good idea. I'll think about it. I think what everyone would like to see is a Rails application getting deployed into a JavaEE container.
  reply
• 

  student1

  6 months ago

  Yes I would like to see Rails application getting deployed into JavaEE
  
  Are there other reasons for JRuby, such as performance reason ?
  
  Thanks
  reply
• 

  xertroyt

  6 months ago

  JRuby performs as well or better that the "sandard" Ruby interpreter.
  
  The big advantage of JRuby for web apps is that the JavaEE container can have multiple "Rails" applications running in the same container.
  
  Until recently, in the conventional Rails world, one would literally run multiple copies of Rails on the same physical server.
  
  This blog posting goes over some of the options.
  
  http://weblogs.java.net/blog/arungupta/archive/...
  reply
• 

  Lisandro

  6 months ago

  Im interested in seeing how an app gets deployed into JEE container, i think it'll be more practical for me to see this mesh in with JEE :)
  reply
• 

  xtine78

  6 months ago

  Has anyone else had any problems with the flash messages using the restful authentication plugin?
  reply
• 

  xertroyt

  6 months ago

  Such as?
  
  -- which message?
  -- Are you trying to display it on a page you created, or one of the standard ones?
  reply
• 

  xtine78

  6 months ago

  The flash messages are not showing up on either the standard or pages I've created. I have verified that the following is included in my code:
  
  <% if flash[:notice] %>
  <div id="notice"><%= flash[:notice] %></div>
  <% end %>
  
  [edit]
  
  which is pointless if your div doesn't match and if you also haven't put in code for flash[:error]! NEVERMIND!
  reply
• 

  swithin

  5 months ago

  I got restful authentication working and merged with my application. THANKS for the Screen Cast, Yah!
  
  I notice when I migrate down, and then back up that my User record (that Restful Auth uses for my login) does not get repopulated in the User table, even though I have a "..._data_add_users.rb" file like my other data migrations. There some trigger or something that does the following message:
  
  Migrating to DataAddUsers (110)
  ←[4;35;1mUser Load (0.000000)←[0m ←[0mSELECT * FROM "users" ←[0m
  WARNING: Can't mass-assign these protected attributes: salt, updated_at, activat
  ed_at, crypted_password, deleted_at, remember_token_expires_at, activation_code,
  id, remember_token, state, created_at
  ←[4;36;1mSQL (0.000000)←[0m ←[0;1mSELECT "login" FROM "users" WHERE ("users"
  .login = 'swithin') ←[0m
  ←[4;35;1mSQL (0.000000)←[0m ←[0mSELECT "email" FROM "users" WHERE ("users".e
  mail = 'josh@swithin.com') ←[0m
  ←[4;36;1mSQL (0.141000)←[0m ←[0;1mINSERT INTO schema_migrations (version) VA
  LUES ('110')←[0m
  ←[4;35;1mSQL (0.000000)←[0m ←[0m SELECT name
  FROM sqlite_master
  WHERE type = 'table' AND NOT name = 'sqlite_sequence'
  ←[0m
  ←[4;36;1mSQL (0.000000)←[0m ←[0;1mSELECT version FROM schema_migrations←[0m
  ←[4;35;1mSQL (0.000000)←[0m ←[0m SELECT name
  FROM sqlite_master
  WHERE type = 'table' AND NOT name = 'sqlite_sequence'
  ←[0m
  ←[4;36;1mSQL (0.000000)←[0m ←[0;1mPRAGMA index_list("users")←[0m
  ←[4;35;1mSQL (0.000000)←[0m ←[0mPRAGMA index_info('index_users_on_login')←[0
  m
  
  It takes time to re-authenticate with waiting for the round-trip email verification.
  Can I turn the "trigger" off so that the data record gets remigrated?
  reply
• 

  xertroyt

  5 months ago

  I don't know how to do this -- omit the callbacks but only during a migration. You could inspect the schema and write raw SQL for the migration to copy the data properly.
  reply
• 

  swithin

  5 months ago

  I am going to just try to remember not to do a total reverse migration to "version=0". I have the User table "create" and "data add" migrations as the first two in the stack. I renumbered the "data add" one to something that is easy to remember "0110_data_add_users.rb". So now I'll just migrated down to "version=0200", or the one just after it. That way those records won't get expunged.
  reply