[Gsoap2-develop] gSOAP 2.5.2 Issue
Development toolkit for Web Services and XML data bindings for C & C++
Brought to you by:
engelen
From: Sharma, A. <ami...@fi...> - 2004-03-08 09:59:24
|
Hi All, I am currently working on Windows XP using gSOAP 2.5.2 stable and using Visual C++ 6.0 for compiling C++ code. I use "wsdl2h.exe" to successfully generate the header file from the wsdl file. However, when I use "soapcpp2" to generate proxy/stub , I get following errors : Compliance Warning: array 'struct ArrayOf_USCOREtns6_USCOREStdErrorMessage' is not compliant with WS-I Basic Profile 1.0a, reason: SOAP encoded array Compliance Warning: array 'struct ArrayOf_USCOREtns2_USCORERoleDTO' is not compliant with WS-I Basic Profile 1.0a, reason: SOAP encoded array Compliance Warning: array 'struct ArrayOf_USCOREtns5_USCOREEnvironment' is not compliant with WS-I Basic Profile 1.0a, reason: SOAP encoded array The three types appearing in the warning messages are represented as soap-encoded arrays in the WSDL file as : <complexType name="ArrayOf_tns6_StdErrorMessage"> <complexContent> <restriction base="soapenc:Array"> <attribute ref="soapenc:arrayType" wsdl:arrayType="tns3:StdErrorMessage[]" /> </restriction> </complexContent> </complexType> <complexType name="ArrayOf_tns2_RoleDTO"> <complexContent> <restriction base="soapenc:Array"> <attribute ref="soapenc:arrayType" wsdl:arrayType="tns4:RoleDTO []" /> </restriction> </complexContent> </complexType> <complexType name="ArrayOf_tns5_Environment"> <complexContent> <restriction base="soapenc:Array"> <attribute ref="soapenc:arrayType" wsdl:arrayType="tns5:Environment []" /> </restriction> </complexContent> </complexType> Subsequent to this, when I call a method of the service using the client generated(C++), it gives me "Access Violation". While debugging, it was noticed that one of the methods in the function trace after calling the method of the services uses a pointer of "ArrayOf_USCOREtns5_USCOREEnvironment" which when referenced leads to "violation". If any of you spare a look at the attached WSDL file, all the three types appearing in the warning messages are SOAP-encoded array types. Could any one please suggest what may be done to eliminate the problem? Please let me know if more input is required on this. Thanks, Amit |