after my complaint on his blog, Nick kindly provided a “verbose build”
of JRuby-Rack which now provides stack traces for errors during Rails
startup. Thanks to this, I was able to figure out what prevents my
Rails app from starting (it runs fine when packaged with warbler 0.9.5):
The sweeper is set as an observer in environment.rb (like this:
config.active_record.observers = :my_sweeper), if I remove it
everything else seems to work fine.
As I’m not too familiar with the innards of how Rails magically loads
dependecies, any hints on what’s going wrong here would be greatly
appreciated!
Found a workaround for my issue: as Nick’s Rack adapter loads
ActionController to hook into the Rails boot sequence, the Sweeper
class won’t get defined because it depends on ActiveRecord being
loaded already. So if I do a simple ‘require “rubygems”; require
“active_record”’ in environment.rb, everything is in order again.
Something like this might also work for the JIRA issue mentioned.
Of course, there might be a cleaner solution – but I’m happy for now 8)
Found a workaround for my issue: as Nick’s Rack adapter loads
ActionController to hook into the Rails boot sequence, the Sweeper class
won’t get defined because it depends on ActiveRecord being loaded already.
So if I do a simple ‘require “rubygems”; require “active_record”’ in
environment.rb, everything is in order again. Something like this might also
work for the JIRA issue mentioned.
Of course, there might be a cleaner solution – but I’m happy for now 8)
D’oh! Nice find. I shouldn’t be loading action_controller in that way.
I’ll try to find a different way to do it.
Cheers,
/Nick
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.