Geoff Youngs wrote: >In the latest ruby package for Debian (1.8.2-9, or >lib/soap/mapping/registry.rb r1.10 in ruby-lang.org CVS) >SOAP::Mapping::Registry#find_mapped_soap_class(target_obj_class) >returns a SOAP::Mapping::BasetypeFactory object instead of an array. > > [snip]
>Two solutions spring to mind: > 1/ Temporarily revert the soap bindings in the ruby package so that > rails continues to work for the time being > 2/ Wait for a fix from upstream for > actionwebservice/lib/action_web_service/protocol/soap_protocol/marshaler.rb > 3/ Nasty bodge to access the SOAP::Mapping::Registry instance vars in > rails, using a delegate which mimics the old behaviour (as per attached). > >Obviously 2 is preferable, 3 is doable (temporarily) while 1 is harder, >but still only a temporary fix. > > Apparently rails 0.13.0 should be out very soon and this error was already fixed upstream, http://dev.rubyonrails.com/changeset/1409 so hopefully this bug will not be in Debian for any length of time. - Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
