NAKAMURA, Hiroshi wrote:
> soap4r-1.5.6, soap4r-1.5.7 did not work as expected, too.
> 
> The problem is caused by;
> 
>  * Ruby's feature loading system (Kernel#require), plus
>  * RubyGems' hacking to control the feature loading scheme, plus
>  * Rails' hacking to improve performance of the feature loading
> 
> It's caused by ActiveSupport + RubyGems, and soap4r just hits the
> problem.  For now soap4r is the only module that is bundled with Ruby
> and released as a gem.  When another module such as REXML, yaml and so
> on will try to create a gem, same kind of problem must be exposed.
> 
> Workaround of this ActiveSupport + RubyGems problem;
> 
>  1. declaring soap4r gem ('gem "soap4r"') before Rails tries to load any
>     features, or
>  2. sudo rm -rf /usr/local/lib/ruby/1.8/{soap,wsdl,xsd}

The second option seems to work for me and I'll simply leave it that way
until they come up with something better.

I suspected it had something to do with either ActiveSupport or
ActiveRecord(both kept appearing in errors after I'd execute 'rake
db:migrate')

Hope this is fixed soon as I'm too new to Ruby to diagnose this type of
incompatibility.