Eh, a nosotros nos saltaba en development usando script/server (que levanta mongrel)
=/ On Mon, Aug 31, 2009 at 11:49 AM, NachoKB<[email protected]> wrote: > 2009/8/31 Luis Lavena <[email protected]> >> >> Un par de resources sobre el tema: >> >> http://github.com/thoughtbot/clearance/blob/master/CHANGELOG.textile >> "Made the clearance controllers unloadable to stop constant loading errors >> in >> development mode (Nick Quaranto)" >> >> >> http://github.com/thoughtbot/clearance/commit/9e669e4bd98cac22129f3d40642068525844ffd2 >> >> A Rails Ticket: >> >> >> https://rails.lighthouseapp.com/projects/8994/tickets/1999-rails-23-rc1-engine-problem-with-load-order-when-used-with-restful_authentication-and-role_requirement >> >> Parece ser que Engines tiene sus detalles en el concepto de reloading. >> >> Yo por mi parte solo use engines como gemas, no como plugins, asi que >> no hay class reloading en esos casos. > > Buenas puntas. > > Algo raro: en Mongrel no sucede (¿se viene Mongrel para development?), en > Passenger sí (y eso que está con RailsSpawnMethod conservative). > > Gracias, muchachos > > nachokb > > _______________________________________________ > Ruby mailing list > [email protected] > http://lista.rubyargentina.com.ar/listinfo.cgi/ruby-rubyargentina.com.ar > > _______________________________________________ Ruby mailing list [email protected] http://lista.rubyargentina.com.ar/listinfo.cgi/ruby-rubyargentina.com.ar
