axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ramesh Gopal <>
Subject Re: WSDL2C tool
Date Fri, 03 Apr 2009 11:40:55 GMT


I am having the following wsdl.

<?xml version="1.0" encoding="UTF-8" ?> 
<wsdl:definitions targetNamespace="http://xxx/visa_valid" xmlns=""
xmlns:tns="http://xxx/visa_valid" name="visa_valid" xmlns:apachesoap=""
xmlns:soapenc="" xmlns:wsdl=""
xmlns:wsdlsoap="" xmlns:xsd="">

<schema elementFormDefault="qualified" targetNamespace="http:/xxx/visa_valid" xmlns="">

<element name="visa_valid"> 
<element name="in0" type="xsd:string" /> 
<element name="in1" type="xsd:string" /> 
<element name="in2" type="xsd:string" /> 
<element name="visa_validresponse"> 
<element name="out0" type="xsd:string" /> 
<element name="out1" type="xsd:decimal" /> 
<element name="out2" type="xsd:decimal" /> 
<wsdl:message name="visa_validresp"> 
<wsdl:part name="body" element="tns:visa_validresponse" /> 
<wsdl:message name="visa_validreq"> 
<wsdl:part name="body" element="tns:visa_valid" /> 
<wsdl:portType name="visa_validporttype"> 
<wsdl:operation name="visa_valid"> 
<wsdl:input message="tns:visa_validreq" name="visa_validrequest" /> 
<wsdl:output message="tns:visa_validresp" name="visa_validresponse" /> 
<wsdl:binding name="visa_validsoapbinding" type="tns:visa_validporttype"> 
<wsdlsoap:binding style="document" transport="" />

<wsdl:operation name="visa_valid"> 
<wsdlsoap:operation soapAction="" /> 
<wsdlsoap:body use="literal" /> 
<wsdlsoap:body use="literal" /> 
<wsdl:service name="ws_visa"> 
<wsdl:port binding="tns:visa_validsoapbinding" name="visa_validservice"> 
<wsdlsoap:address location="http://<ip>:<port>/axis2/services/ws_visa" />


Now when I try to generate the client code using the command:

java org.apache.axis2.wsdl.WSDL2C -uri <wsdl_file> -sd -d none

it generates the client stub.

However, there is a lot of difference between the WSDL2JAVA and WSDL2C tools.

The WSDL2C generates the code taking a node as an input value. Then it becomes imperative
that the user forms the xml request and sends it.
But in WSDL2Java, it just needs a value for input (The value can be either a string / integer/
decimal etc value).
Is this a expected behaviour with WSDL2C ????

Does WSDL2C only cater to SOAP requests ? I dont see any code being generated for HTTP / MQ
requests ?

--- On Thu, 2/4/09, ramesh Gopal <> wrote:

> From: ramesh Gopal <>
> Subject: WSDL2C tool
> To: "Apache AXIS C User List" <>
> Date: Thursday, 2 April, 2009, 11:20 AM
> Hello,
> I have used WSDL2C (taking input as a wsdl file) to
> generate the a client code using the command mentioned below
> :
> java org.apache.axis2.wsdl.WSDL2C -uri <wsdl_file>
> -sd -d none
> Does the WSDL2C parse the wsdl to a point where it can get
> more information about what the input/output datatypes are
> ??? 
> input/output message tags are (eg ... if <max> is an
> input tag does WSDL2C retrieve this information too) ....
> I have used a Web Services explorer tool on Eclipse, and
> saw that this gets all the specific information from a wsdl
> file.
> Its my understanding that expecting the user to know all
> this information from a wsdl (and that too from someone who
> is new to Web service world), how do we see all this
> happening ???
> Rgds,
> Ramesh.
>       Add more friends to your messenger and
> enjoy! Go to

      Add more friends to your messenger and enjoy! Go to

View raw message