Return-Path: 
 <axis-c-user-return-1169-apmail-ws-axis-c-user-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-c-user-archive@www.apache.org
Received: (qmail 4904 invoked from network); 9 Dec 2004 01:46:17 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 9 Dec 2004 01:46:17 -0000
Received: (qmail 65034 invoked by uid 500); 9 Dec 2004 01:46:16 -0000
Delivered-To: apmail-ws-axis-c-user-archive@ws.apache.org
Received: (qmail 65018 invoked by uid 500); 9 Dec 2004 01:46:16 -0000
Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:axis-c-user-help@ws.apache.org>
list-unsubscribe: <mailto:axis-c-user-unsubscribe@ws.apache.org>
list-post: <mailto:axis-c-user@ws.apache.org>
List-Id: "Apache AXIS C User List" <axis-c-user.ws.apache.org>
Reply-To: "Apache AXIS C User List" <axis-c-user@ws.apache.org>
Delivered-To: mailing list axis-c-user@ws.apache.org
Received: (qmail 65003 invoked by uid 99); 9 Dec 2004 01:46:15 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: domain of samisa.abeysinghe@gmail.com
 designates 64.233.184.194 as permitted sender)
Received: from wproxy.gmail.com (HELO wproxy.gmail.com) (64.233.184.194)
  by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 08 Dec 2004 17:46:14 -0800
Received: by wproxy.gmail.com with SMTP id 67so852020wri
        for <axis-c-user@ws.apache.org>; Wed, 08 Dec 2004 17:46:12 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
        b=Cs4Tfcl+y86B8C/J4PkI2mT5DvHsSm2or8EmoWcivAsJFPCLTu5WdEBqbNTeKUCORTSWMlYM26P522+LWrbYjgFfenu+9g+/YxIzB5GhzSYkwvA96LuvMTWFGvFSDRmKTyZ8JzSt7FNGI3ql+UPCdHMZ1pboKFfBQH7HpVXIsSM=
Received: by 10.54.44.73 with SMTP id r73mr1061858wrr;
        Wed, 08 Dec 2004 17:46:12 -0800 (PST)
Received: by 10.54.28.30 with HTTP; Wed, 8 Dec 2004 17:46:12 -0800 (PST)
Message-ID: <a0f0c148041208174672f07c33@mail.gmail.com>
Date: Thu, 9 Dec 2004 01:46:12 +0000
From: Samisa Abeysinghe <samisa.abeysinghe@gmail.com>
Reply-To: Samisa Abeysinghe <samisa.abeysinghe@gmail.com>
To: Apache AXIS C User List <axis-c-user@ws.apache.org>
Subject: Re: Problem with serialization of complex parameters in axis C++
 (RCP)
In-Reply-To: 
 <573295DAAC6F2643A1E572F5C7D667370111AF06@tlvmail5.corp.amdocs.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: 
 <573295DAAC6F2643A1E572F5C7D667370111AF06@tlvmail5.corp.amdocs.com>
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Hi Leonid,
    I remember like this problem was there sometime back and was
resolved - most probably in 1.3.
    Are you using 1.3 release already?

    Please send the complete WSDL file attached if possible, so that I
could have a look at the generated code.

Thanks,
Samisa...


On Wed, 8 Dec 2004 16:19:40 +0200, Leonid Gerzon
<leonid.gerzon@amdocs.com> wrote:
>  
> 
> Hello! 
> 
> I have a problem with sending complex parameters 
> 
> to Web Services from axis C++ client (in RPC style). 
> 
> Axis C++ serializes complex types as follows: 
> 
> it puts the parameter type in both: name and type fields. 
> 
> But if such a complex type is a member of another complex type, 
> 
> then its name may be different from its type. 
> 
> Here what is in my WSDL (types): 
> 
>    <complexType name="DigitalRightPermission"> 
> 
>     <sequence> 
> 
>      <element name="descr" type="xsd:string"/> 
> 
>     </sequence> 
> 
>    </complexType> 
> 
>    <complexType name="ServiceGroup"> 
> 
>     <sequence> 
> 
>      <element minOccurs="0" maxOccurs="1" name="dp"
> type="DigitalRightPermission"/> 
> 
>     </sequence> 
> 
>    </complexType> 
> 
> here what is in soap request (sent by axis C++ client): 
> 
>             <ServiceGroup type="ServiceGroup"> 
> 
>                <DigitalRightPermission type="DigitalRightPermission"> 
> 
>                  <descr type="xsd:string">THE DESCRIPTION</descr> 
> 
>                </DigitalRightPermission> 
> 
>             </ServiceGroup> 
> 
> and I receive an error response from axis java server that tag
> DigitalRightPermission 
> 
> is wrong. 
> 
> here how it should look in soap: 
> 
>             <ServiceGroup type="ServiceGroup"> 
> 
>                <dp type="DigitalRightPermission"> 
> 
>                  <descr type="xsd:string">THE DESCRIPTION</descr > 
> 
>                </dp> 
> 
>             </ServiceGroup> 
> 
> Is it a bug in axis C++ code or I need to configure axis C++ so it will use
> right serialization of complex objects? 
> 
> Thanks in advance, 
> 
> Leonid Gerzon. 
>  
> The information contained in this message is proprietary of Amdocs,
>  protected from disclosure, and may be privileged.
>  The information is intended to be conveyed only to the designated
> recipient(s)
>  of the message. If the reader of this message is not the intended
> recipient,
>  you are hereby notified that any dissemination, use, distribution or
> copying of 
>  this communication is strictly prohibited and may be unlawful. 
>  If you have received this communication in error, please notify us
> immediately
>  by replying to the message and deleting it from your computer.
>  Thank you.
>