-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Eric H. wrote:
> Seems this was caused by soap4r-1.5.8, removing it and using only 1.5.7
> fixed the problem. I happened to do a search and found that someone was
> having problems starting Mongrel if they had 1.5.8 installed so I tried
> it and viola! it worked.

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}

Regards,
// NaHi

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)

iQEVAwUBRv77Zh9L2jg5EEGlAQIVpggAtAOO63eva5paqDSOGIzju/yDgUgUrhER
Adv+WsOnaoohuzPkse3gvtbfNeGQZqti6fQ5kGqaEmgOZM0XYuqaY+h3N07SRNFD
biUy8VIAhVeVdGJ8pCWbspfSYpfb7lp+WJPGsF+pmIoceQJalZf16/YxoYJULOhY
6OkiKT4L/h/A6bLKOrOjj3OqqLUXm2KDb8cBYmQbgCUPkBDqyeWF5QtXI2iAKNRb
P4P1OQ2WzQCv4eWO+u8XhgVjmXfuZVAYhRhXrzWs0KO4j2BhIhnYjN0Yoaun+s5y
mwA26iqtpxC2a1a7zd6fppl6Uocwl8BJSNO3kCf5oKqJ9ScStCgqvg==
=fEue
-----END PGP SIGNATURE-----