axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Resolved: (AXISCPP-36) A bug about WSDL2Ws
Date Fri, 09 Apr 2004 04:24:43 GMT

   The following issue has been resolved as FIXED.

   Resolver: Susantha Kumara
       Date: Thu, 8 Apr 2004 9:23 PM

WSDL2Ws tool improved to consider parameterOrder attribute of an operation and preserve its
View the issue:

Here is an overview of the issue:
        Key: AXISCPP-36
    Summary: A bug about WSDL2Ws
       Type: Bug

     Status: Resolved
 Resolution: FIXED

    Project: Axis-C++
             WSDL processing
   Fix Fors:
             current (nightly)
             1.0 Beta

   Reporter: leo mok

    Created: Mon, 5 Jan 2004 9:05 AM
    Updated: Thu, 8 Apr 2004 9:23 PM
Environment: Operating System: Other
Platform: PC

I use axis as web service server. and the Java Interface is like this:
public void test(java.lang.String in0, java.lang.String in1, java.lang.String 
in2, java.lang.String in3);
the generate wsdl seg is :
   <wsdl:message name="testRequest">
      <wsdl:part name="in0" type="xsd:string"/>
      <wsdl:part name="in1" type="xsd:string"/>
      <wsdl:part name="in2" type="xsd:string"/>
      <wsdl:part name="in3" type="xsd:string"/>
but WSDL2Ws generate like this:
	m_pCall->SetOperation("test", "urn:EchoService");
	m_pCall->AddParameter(Value0, "in2", XSD_STRING);
	m_pCall->AddParameter(Value1, "in0", XSD_STRING);
	m_pCall->AddParameter(Value2, "in1", XSD_STRING);
	m_pCall->AddParameter(Value3, "in3", XSD_STRING);

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message