In some rev after 3630, starting to run into an ActionWebService issue.
I remember some recent thread (I think on rails-core) that mentioned
something about an issue with a #parent method, but I can''t find that
thread.
I also couldn''t find any apparent change between 3630 and 3672 that
would cause this to break, but it''s gotta be there somewhere.
Does anyone recall the #parent issue?
/usr/pkg/ruby184/lib/ruby/1.8/soap/baseData.rb:69:in `rootnode'':
undefined method `parent'' for
#<SOAP::Parser::ParseFrame::NodeContainer:0x402fdc4c @node=nil>
(NoMethodError)
from
/usr/pkg/ruby184/lib/ruby/1.8/soap/encodingstyle/soapHandler.rb:566:in
`decode_resolve_id''
from /usr/pkg/ruby184/lib/ruby/1.8/rexml/encoding.rb:37:in
`find_all''
from
/usr/pkg/ruby184/lib/ruby/1.8/soap/encodingstyle/soapHandler.rb:557:in
`decode_resolve_id''
from
/usr/pkg/ruby184/lib/ruby/1.8/soap/encodingstyle/soapHandler.rb:212:in
`decode_epilogue''
On Mon, Feb 27, 2006 at 11:35:35AM -0800, Michael Schoen wrote:> In some rev after 3630, starting to run into an ActionWebService issue. I remember some recent thread (I think on rails-core) that > mentioned something about an issue with a #parent method, but I can''t find that thread. > > I also couldn''t find any apparent change between 3630 and 3672 that would cause this to break, but it''s gotta be there somewhere. > > Does anyone recall the #parent issue? > > > /usr/pkg/ruby184/lib/ruby/1.8/soap/baseData.rb:69:in `rootnode'': undefined method `parent'' for > #<SOAP::Parser::ParseFrame::NodeContainer:0x402fdc4c @node=nil> (NoMethodError) > from /usr/pkg/ruby184/lib/ruby/1.8/soap/encodingstyle/soapHandler.rb:566:in `decode_resolve_id'' > from /usr/pkg/ruby184/lib/ruby/1.8/rexml/encoding.rb:37:in `find_all'' > from /usr/pkg/ruby184/lib/ruby/1.8/soap/encodingstyle/soapHandler.rb:557:in `decode_resolve_id'' > from /usr/pkg/ruby184/lib/ruby/1.8/soap/encodingstyle/soapHandler.rb:212:in `decode_epilogue'' > > _______________________________________________ > Rails-core mailing list > Rails-core@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails-coreI''ve yet to run in to this, we''re busy tracking down the ''Unable to modify frozen object'' coming from the new soap4r in 1.8.4, has to do with the EMPTY = Qname.new.freeze at the bottom of the xsd/qname.rb. This is apparently what''s populating the qname for every parameter request. We''ve targeted Thursday, march 2 for troubleshooting this problem. Can you tell me what ruby installer you used, platform, and some code to isolate the issue? -- TJ Vanderpoel GCIA,GCIH tj@rapidreporting.com _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
TJ Vanderpoel wrote:> I''ve yet to run in to this, we''re busy tracking down the ''Unable to modify > frozen object'' coming from the new soap4r in 1.8.4, has to do with > the EMPTY = Qname.new.freeze at the bottom of the xsd/qname.rb. This is > apparently what''s populating the qname for every parameter request. We''ve > targeted Thursday, march 2 for troubleshooting this problem. Can you tell > me what ruby installer you used, platform, and some code to isolate the issue?Ruby 1.8.4, installed from source on Debian. I''ll try to get you some isolated code to reproduce.
Am Montag, den 27.02.2006, 11:35 -0800 schrieb Michael Schoen:> In some rev after 3630, starting to run into an ActionWebService issue. > I remember some recent thread (I think on rails-core) that mentioned > something about an issue with a #parent method, but I can''t find that > thread. > > I also couldn''t find any apparent change between 3630 and 3672 that > would cause this to break, but it''s gotta be there somewhere. > > Does anyone recall the #parent issue? > > > /usr/pkg/ruby184/lib/ruby/1.8/soap/baseData.rb:69:in `rootnode'': > undefined method `parent'' for > #<SOAP::Parser::ParseFrame::NodeContainer:0x402fdc4c @node=nil> > (NoMethodError) > from > /usr/pkg/ruby184/lib/ruby/1.8/soap/encodingstyle/soapHandler.rb:566:in > `decode_resolve_id'' > from /usr/pkg/ruby184/lib/ruby/1.8/rexml/encoding.rb:37:in > `find_all'' > from > /usr/pkg/ruby184/lib/ruby/1.8/soap/encodingstyle/soapHandler.rb:557:in > `decode_resolve_id'' > from > /usr/pkg/ruby184/lib/ruby/1.8/soap/encodingstyle/soapHandler.rb:212:in > `decode_epilogue''I ran in exactly the same problem and found the cause: The SOAP request was redirected because of a configuration problem and some HTML was returned. That HTML did not get through the response parser, what is no surprise. -- Norman Timmler http://blog.inlet-media.de
> I ran in exactly the same problem and found the cause: The SOAP request > was redirected because of a configuration problem and some HTML was > returned. That HTML did not get through the response parser, what is no > surprise.Yep, in my case it was a result of some routing issue, that got caught in the routing change in r3636. I don''t know routes well enough to sort it out, so I just hacked it to go back to the old functionality (which just ignored all NameError''s as it resolved the route).