Return-Path: 
 <axis-user-return-80170-apmail-ws-axis-user-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-user-archive@www.apache.org
Received: (qmail 39403 invoked from network); 18 Aug 2009 14:28:33 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 18 Aug 2009 14:28:33 -0000
Received: (qmail 80948 invoked by uid 500); 18 Aug 2009 14:28:49 -0000
Delivered-To: apmail-ws-axis-user-archive@ws.apache.org
Received: (qmail 80904 invoked by uid 500); 18 Aug 2009 14:28:49 -0000
Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
list-help: <mailto:axis-user-help@ws.apache.org>
list-unsubscribe: <mailto:axis-user-unsubscribe@ws.apache.org>
List-Post: <mailto:axis-user@ws.apache.org>
List-Id: <axis-user.ws.apache.org>
Delivered-To: mailing list axis-user@ws.apache.org
Received: (qmail 80895 invoked by uid 99); 18 Aug 2009 14:28:49 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Aug 2009 14:28:49 +0000
X-ASF-Spam-Status: No, hits=2.2 required=10.0
	tests=HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of cchinu@gmail.com designates
 209.85.212.193 as permitted sender)
Received: from [209.85.212.193] (HELO mail-vw0-f193.google.com)
 (209.85.212.193)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Aug 2009 14:28:40 +0000
Received: by vws31 with SMTP id 31so3279818vws.28
        for <axis-user@ws.apache.org>; Tue, 18 Aug 2009 07:28:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:date:message-id:subject
         :from:to:content-type;
        bh=tkut1yUFititVvkNKMyBeoJLio68wYyKmXOyEkhOGbs=;
        b=dJ4HC3kj4XpoNmj4/zWbi2Xri4VuGBT4karWh2LsBYwAYC8s9OytIQwqPAsXKFzYOP
         o95nxXICBKRRHPssuR1qLgESLqeMFUU+Ay83iadhS1++G4GJgyFDTH36F8HlO5qjoYn6
         LZKw1XOKVz190NopK0oQR3INqBk0OftnPBjjc=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=mq3YlxvZ94v2sE4f304hGiV5Ib3Uohhfmx+A1jdai+D4mZXsdK6w/BMRtHJ1dFUxSf
         yZY9q5jiwUPgIkOBuBSvV4jI778/3NU0OjTHMuavN9oWlMGFNu5h1A7JggT+N0JtEMyU
         0ZxDAG9BoYqS+1PVds+yp7t8gr3kGhI3tdluI=
MIME-Version: 1.0
Received: by 10.220.10.140 with SMTP id p12mr7016283vcp.66.1250605699136;
 Tue,
	18 Aug 2009 07:28:19 -0700 (PDT)
Date: Tue, 18 Aug 2009 19:58:19 +0530
Message-ID: <a52be6d90908180728m381b47eaj289abfb24a351d0@mail.gmail.com>
Subject: Question about WSDL
From: Chinmoy Chakraborty <cchinu@gmail.com>
To: axis-user@ws.apache.org
Content-Type: multipart/alternative; boundary=0016e64906ac737ea404716b5436
X-Virus-Checked: Checked by ClamAV on apache.org

--0016e64906ac737ea404716b5436
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi All,

I have a service called ABS and the operation name is 'invoke'. The
operation has two parameters, one is String another one is a Float. These
are basic data type but why In the WSDL these data types show as complex
type? We have customers and they are having problems for the complex types
when they try to create stubs from the WSDL. The snippet of WSDL is
following:

.....
<xs:element name="invoke">
                <xs:complexType>
                    <xs:sequence>
                        <xs:element minOccurs="0" name="authToken"
nillable="true" type="xs:string"/>
                        <xs:element minOccurs="0" name="numberC"
type="xs:float"/>
                    </xs:sequence>
                </xs:complexType>
            </xs:element>
.....

Chinmoy

--0016e64906ac737ea404716b5436
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Hi All,</div>
<div>=A0</div>
<div>I have a service called ABS and the operation name is &#39;invoke&#39;=
. The operation has two parameters, one is String another one is a Float. T=
hese are basic data type but why In the WSDL these data types show as compl=
ex type? We have customers and they are having problems for the complex typ=
es when they try to create stubs from the WSDL. The snippet of WSDL is foll=
owing:</div>

<div>=A0</div>
<div>.....</div>
<div>&lt;xs:element name=3D&quot;invoke&quot;&gt;<br>=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0 &lt;xs:complexType&gt;<br>=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 &lt;xs:sequence&gt;<br>=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 &lt;xs:element minOccur=
s=3D&quot;0&quot; name=3D&quot;authToken&quot; nillable=3D&quot;true&quot; =
type=3D&quot;xs:string&quot;/&gt;<br>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 &lt;x=
s:element minOccurs=3D&quot;0&quot; name=3D&quot;numberC&quot; type=3D&quot=
;xs:float&quot;/&gt;<br>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0 &lt;/xs:sequence&gt;<br>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 &lt;/xs:complexType&gt;<br>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 &lt;/xs:el=
ement&gt;</div>

<div>.....</div>
<div>=A0</div>
<div>Chinmoy</div>
<div>=A0</div>

--0016e64906ac737ea404716b5436--