Additional problems with WSDL described in AXISCPP-693
------------------------------------------------------

         Key: AXISCPP-697
         URL: http://issues.apache.org/jira/browse/AXISCPP-697
     Project: Axis-C++
        Type: Bug
 Environment: n/a
    Reporter: Fred Preston
 Assigned to: Fred Preston 


Using the WSDL and XSD described in AXICPP-693, another problem has been 
uncovered in the web service header file.

Test.hpp
------------
*
 * This file was auto-generated by the Axis C++ Web Service Generator (WSDL2Ws)
 * This file contains Client Stub Class for remote web service 
 */

#if !defined(__Test_A_CLIENTSTUB_H__INCLUDED_)
#define __Test_A_CLIENTSTUB_H__INCLUDED_

#include <axis/client/Stub.hpp>
#include <axis/OtherFaultException.hpp>
#include <axis/ISoapFault.hpp>
AXIS_CPP_NAMESPACE_USE
#include "MyClass.hpp"

class Test_A:public Stub
{
public:
 STORAGE_CLASS_INFO Test_A(const char* pchEndpointUri, AXIS_PROTOCOL_TYPE 
eProtocol=APTHTTP1_1);
 STORAGE_CLASS_INFO Test_A();
public:
 STORAGE_CLASS_INFO virtual ~Test_A();
public: 
 STORAGE_CLASS_INFO void SetSecure( char *, ...);
 STORAGE_CLASS_INFO void add(>MyClass_Name Value0, >MyClass_Values Value1, 
xsd__NMTOKEN Value2);

private:
 void includeSecure();

protected:
 std::string sArguments[8];
};

#endif /* !defined(__Test_A_CLIENTSTUB_H__INCLUDED_)*/

In the public declarations, the method 'add' has a prototype with three 
parameters.  The types of these parameters should be;- xsd__string,  
XSD__base64Binary and xsd__NMTOKEN.  In the header they are defined as 
follows;- >MyClass_Name, >MyClass_Values and xsd__NMTOKEN.  This looks like the 
two complex types are not being properly decoded.  The cpp file is correct and 
the method has the following definition;- void Test_A::add(xsd__string Value0, 
xsd__base64Binary* Value1, xsd__NMTOKEN Value2).


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to