search for: controller_class

...# FIXME: Bug in swig! #@settings.port = port - @settings.mechanism = 'GSSAPI' + #@settings.mechanism = 'GSSAPI' @logger.info "Connecting to broker on #{@settings.host}.." @@ -165,7 +165,7 @@ class OvirtAgent < Qmf::AgentHandler end @controller_classes.values.each do |controller_class| - @logger.info "Register #{controller_class.schema_class.name} => #{controller_class.name}" + @logger.info "Register #{controller_class.schema_class.name} => #{controller_class.name}, id #{controller_class.schema_class.id}"...

I remember having this discussion on IRC before, so Ezra if you could remind me that would be appreciated: Why do we check for the existence of the controller file in (what is now) Request#controller_class? The reason I ask is that I would like to implement some sort of "Rails engine" like features for gem plugins--in other words, drop in a gem that has controllers/views etc. and have it just work. In order to do this, I need the Request#controller_class to return my gem''...

Hi All, I need to run some reports via cron. I know I can use runner and call a method in a model class. But I''d really like to use templates and IMO this kind of logic belongs in a controller anyways. These are periodic reports so I don''t need nor want to leave a server running all the time, so getting the data via curl/wget isn''t really an option. What I really

I''m only just learning to use Rails, but this seems like something very out of my control. I used GEM to download and install Rails, then created a new application and a controller and started the WEBrick server. When I try to access the new controller "Test" using http://localhost:3000/test/ I get a "Not Found" error and a great deal of output from the server

Hello, Has anyone already come up with a set of shared behaviours that someone could leverage when adhering to a CRUD concept, with respect to controllers? Relatedly, it would be nice if there were a way to share generalized behaviour specs. -Chris

In rspec_on_rails, method setup_with_controller, exists the following line: @controller_class.send(:define_method, :rescue_action) { | e| raise e } I understand that this is a better way to handle errors than the default. However, it gets in the way when you''ve defined your own rescue_action and are trying to test it. No good solutions came to me while I pondered the proble...

A couple days ago I submitted a patch, that was committed by Ezra, to the MrBlog project for the Rspec on Merb plugin. So far, it only works with ActiveRecord including fixtures. Has any played with it? If so, did you get it to work? I''m going to be submitting a patch for Controller specs soon. It will be very bare bones, given my current lack of understanding of Merb controller

hi all, I want to move some routing tasks out of the router and into the controller. The goal is to make Merb feel less like mod_rewrite and give the user more control at the controller. The new Router is simple: it takes the path_info (not the whole request) then outputs a controller class and some parameters from the path matching. The rest of the routing would be done at the controller level.