Return-Path: 
 <axis-user-return-44062-apmail-ws-axis-user-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-user-archive@www.apache.org
Received: (qmail 87705 invoked from network); 7 May 2006 22:09:24 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 7 May 2006 22:09:24 -0000
Received: (qmail 32693 invoked by uid 500); 7 May 2006 22:09:15 -0000
Delivered-To: apmail-ws-axis-user-archive@ws.apache.org
Received: (qmail 31621 invoked by uid 500); 7 May 2006 22:09:12 -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 31599 invoked by uid 99); 7 May 2006 22:09:12 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 May 2006 15:09:12 -0700
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=HTML_MESSAGE,UNPARSEABLE_RELAY
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Received: from [192.18.98.31] (HELO brmea-mail-1.sun.com) (192.18.98.31)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 May 2006 15:09:11 -0700
Received: from fe-amer-03.sun.com ([192.18.108.177])
	by brmea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id k47M8oSX001923;
	Sun, 7 May 2006 16:08:51 -0600 (MDT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-4.02 (built Sep  9 2005))
 id <0IYX000011H5AJ00@mail-amer.sun.com>
 (original mail from Rajeev.Gupta@Sun.COM); Sun,
 07 May 2006 16:08:50 -0600 (MDT)
Received: from [192.18.191.116] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-4.02 (built Sep  9 2005))
 with ESMTPSA id <0IYX006QA1IQ8Y00@mail-amer.sun.com>; Sun,
 07 May 2006 16:08:50 -0600 (MDT)
Date: Sun, 07 May 2006 15:10:11 -0700
From: Rajeev Gupta <Rajeev.Gupta@Sun.COM>
Subject: Apache 1.3+ Question (possible bug)
Sender: Rajeev.Gupta@Sun.COM
To: axis-dev@ws.apache.org, axis-user@ws.apache.org
Reply-to: Rajeev.Gupta@Sun.COM
Message-id: <445E7043.8060703@sun.com>
Organization: SUN Microsystems
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_+F+cCsqDIsF+imYToBgwzA)"
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

This is a multi-part message in MIME format.

--Boundary_(ID_+F+cCsqDIsF+imYToBgwzA)
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

  Hi There,

I am seeing this weird behavior with Axis 1.3 (and also Axis 1.4), where 
my client stubs are not generated correctly.

I have the following complex type in my WSDL file:

<complexType name="IDSessionData">
    <sequence>
        <element name="eSessionIdentifier" type="string" nillable="true"/>
        <element name="sessionIdentifier" type="string" nillable="true"/>
        <element name="userProfile" type="tns:IDUserProfile" 
nillable="true"/>
    </sequence>
</complexType>

<complexType name="IDUserProfile">
        <sequence>
           <element name="profileAttributes" type="tns:IDUserAttribute" 
nillable="true" minOccurs="0" maxOccurs="unbounded"/>
        </sequence>
</complexType>


Axis is not generating IDUserProfile class file on the client side at 
all. It's generating IDSessionData with an array of IDUserAttribute 
directly - looks like it's trying to optimize something.... or thinking 
of IDUserPrifile as an element. When I send a soapRequest with 
IDUserAttribute array as part of IDSessionData, the server doesn't 
understand that - which is obvious.

Any idea why this is happening? Is it because of a bad WSDL? or is it a 
bug in Axis 1.3 (and Axis 1.4)
Note: Axis 1.1 is working perfectly fine here....

Thanks,

-- 
Rajeev 



--Boundary_(ID_+F+cCsqDIsF+imYToBgwzA)
Content-type: text/html; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<div class="moz-text-html" lang="x-western"> Hi There,<br>
<br>
I am seeing this weird behavior with Axis 1.3 (and also Axis 1.4),
where my client stubs are not generated correctly. <br>
<br>
I have the following complex type in my WSDL file:<br>
<br>
<div><small><font face="Courier New">&lt;complexType
name="IDSessionData"&gt;<br>
&nbsp;&nbsp;&nbsp; &lt;sequence&gt;<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &lt;element name="eSessionIdentifier" type="string"
nillable="true"/&gt;<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &lt;element name="sessionIdentifier" type="string"
nillable="true"/&gt;<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &lt;element name="userProfile" type="tns:IDUserProfile"
nillable="true"/&gt;<br>
&nbsp;&nbsp;&nbsp; &lt;/sequence&gt;<br>
&lt;/complexType&gt;<br>
<br>
&lt;complexType
name="IDUserProfile"&gt;</font></small></div>
<div><small><font face="Courier New">&nbsp; &nbsp; &nbsp; &nbsp; &lt;sequence&gt;</font></small></div>
<div><small><font face="Courier New">&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &lt;element name="profileAttributes"
type="tns:IDUserAttribute" nillable="true" minOccurs="0"
maxOccurs="unbounded"/&gt;</font></small></div>
<div><small><font face="Courier New">&nbsp; &nbsp; &nbsp; &nbsp; &lt;/sequence&gt;</font></small></div>
<div><small><font face="Courier New">&lt;/complexType&gt;<br>
<br>
</font></small><tt><br>
</tt><tt>Axis is not generating IDUserProfile class file on the client
side at all. It's generating IDSessionData with an array of
IDUserAttribute
directly - looks like it's trying to optimize something.... or thinking
of IDUserPrifile as an element. When I
send a soapRequest with IDUserAttribute array as part
of IDSessionData, the server doesn't understand that - which is
obvious. </tt><br>
</div>
<br>
<tt>Any idea why this is happening? Is it because of a bad WSDL? or is
it a bug in
Axis 1.3 (and Axis 1.4) </tt><br>
<tt>Note: Axis 1.1 is working perfectly fine here....</tt><br>
<br>
Thanks,<br>
<pre class="moz-signature" cols="72">-- 
Rajeev 

</pre>
</div>
</body>
</html>

--Boundary_(ID_+F+cCsqDIsF+imYToBgwzA)--