[#8815] Segfault in libc strlen, via rb_str_new2 — "Sean E. Russell" <ser@...>

Howdy,

12 messages 2006/09/09
[#8817] Re: Segfault in libc strlen, via rb_str_new2 — Eric Hodel <drbrain@...7.net> 2006/09/09

On Sep 8, 2006, at 10:10 PM, Sean E. Russell wrote:

[ ruby-Bugs-5763 ] Problem with generated soap requests / classes using the WSDL Tools

From: <noreply@...>
Date: 2006-09-14 22:53:20 UTC
List: ruby-core #8874
Bugs item #5763, was opened at 2006-09-14 17:52
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=5763&group_id=426

Category: Standard Library
Group: 1.8.5
Status: Open
Resolution: None
Priority: 3
Submitted By: David Sledge (dsledge)
Assigned to: Nobody (None)
Summary: Problem with generated soap requests / classes using the WSDL Tools

Initial Comment:
When using the SOAP::WSDLDriverFactory to talk to webservices the form tag of some elements is not honored. If you look at the wsdl in the attached test app you will see that the schemas 'elementFormDefault="qualified"' but the complexType sequence elements have a 'form="unqualified"' tag. The generated soap request is not correct. It adds the namespace for the sequence elements of the complexType anyway. This also happens with the classes generated using the WSDL2Ruby class to generate classdef's. I was able to get around it by generating a driver with WSDL2Ruby and setting the flag on the in parameters to false and then modifying the classdef generated file for the complexType to have nil namespaces in the @@schema_element. Also it seems wrong for the response that I do not have to set the flag on the out parameters of the generated driver class to false or change the @@schema_element in the classdef generated file and it still properly handlers the response xml that does n
 ot have the namespace on its complex type sequence elements.

The test app will give an exception because there is no webservice server running but it still generates the request data logged in the "logs" directory.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=5763&group_id=426

In This Thread

Prev Next