axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kiran Kumar" <kku...@objectwave.com>
Subject RE: <item> in Arrays
Date Wed, 08 Mar 2006 17:19:29 GMT
Hi,

As per the definition of your WSDL, the generated output is correct.

In your WSDL, "LISTA1" is defined as an Array of type 'ArrayOP58OLISTA1', so your result will
be

<LISTA1> .. </LISTA1>
<LISTA1> .. </LISTA1>
<LISTA1> .. </LISTA1>

But if you want 

<LISTA1>
   <item> .. </item>
   <item> .. </item>
</LISTA1>

then your WSDL should have 

      <complexType name="ResultBeanOP58">
        <sequence>
          <element name="CEMPRESA" nillable="true" type="string" />
          <element name="LISTA1" nillable="true" type="LISTA1Type"/>
          <element name="ZINDEURO" nillable="true" type="string" />
        </sequence>
      </complexType>
      <complexType name="LISTA1Type">
	<sequence>
	   <element name="item" type="transactionHB24:ArrayHB24ILISTA1" maxOccurs="unbounded"/>
 	</sequence>
     </complexType>      
      <complexType name="ArrayOP58OLISTA1">
        <sequence>
          <element name="CREDITO" nillable="true" type="string" />
          <element name="DDIAOP" nillable="true" type="string" />
          <element name="DEBITO1" nillable="true" type="string" />
        </sequence>

So you may have to see what is the actual error you are getting on the server side, and make
sure you are using the right WSDL.

Kiran

-----Original Message-----
From: Pedro Alves [mailto:pedro@neraka.no-ip.org]
Sent: Wed 3/8/2006 10:30 AM
To: axis-user@ws.apache.org
Subject: Re: <item> in Arrays
 
On Wed, Mar 08, 2006 at 09:39:07AM -0600, Kiran Kumar wrote:
> Hi,
> 
> As per the definition of type'ArrayHB24ILISTA1' is not 'Array'.. You have to define array
of your complex type (ArrayHB24ILISTA1).. It would be something like this :
> 
> 	<xsd:complexType name="LISTA1Type">
> 		<xsd:sequence>
> 			<xsd:element name="item" type="transactionHB24:ArrayHB24ILISTA1" maxOccurs="unbounded"/>
> 		</xsd:sequence>
> 	</xsd:complexType>
> 
>        <xsd:element name="LISTA1" type="LISTA1Type" />
> 
> 
> Name of the your complex type (ArrayHB24ILISTA1) is confusing..Its not an array.. its
just a complex type.
> 
> Kiran
> 


But what puzzles me is that this output

 
           <LISTA1 xmlns:bean="java:com.altitude.tp.transactions.transactionOP58" xsi:type="SOAP-ENC:Array"
SOAP-ENC:arrayType="bean:ArrayOP58OLISTA1[18]">
             <item xmlns:bean="java:com.altitude.tp.transactions.transactionOP58" xsi:type="bean:ArrayOP58OLISTA1">
               <GDESMOV xsi:type="xsd:string">Imp Selo TRF-190</GDESMOV>
               <ZCHQ xsi:type="xsd:string">0</ZCHQ>
               <DEBITO1 xsi:type="xsd:string">0.00</DEBITO1>
             </item>
           </LISTA1>
 

is generated after this wsdl:

      <complexType name="ResultBeanOP58">
        <sequence>
          <element name="CEMPRESA" nillable="true" type="string" />
          <element name="LISTA1" nillable="true" type="transactionOP58:ArrayOP58OLISTA1"
maxOccurs="unbounded" />
          <element name="ZINDEURO" nillable="true" type="string" />
        </sequence>
      </complexType>
      <complexType name="ArrayOP58OLISTA1">
        <sequence>
          <element name="CREDITO" nillable="true" type="string" />
          <element name="DDIAOP" nillable="true" type="string" />
          <element name="DEBITO1" nillable="true" type="string" />
        </sequence>


I really cannot tell any differences


Pedro


> > On 3/8/06, Pedro Alves <pedro@neraka.no-ip.org > wrote:
> > 
> > 
> > 
> >     Hi.
> > 
> >     I have a wsdl that has this element in the request:
> > 
> >     <element name="LISTA1" nillable="true"
> >     type="transactionHB24:ArrayHB24ILISTA1" maxOccurs="unbounded" />
> > 
> > 
> >     When I invoke the ws, the soap has the form:
> > 
> >     <...>
> >         <LISTA1>...</LISTA1>
> >         <LISTA1>...</LISTA1>
> >         <LISTA1>...</LISTA1>
> >         <LISTA1>...</LISTA1>
> >     <...>
> > 
> >     But the other side throws an exception. I think the other side is expecting
> > 
> >     <...>
> >         <LISTA1>
> >             <item>...</item>
> >             <item>...</item>
> >         </LISTA1>
> >     <...>
> > 
> >     I know that axis can handle this kind of semantics because It can parse
> >     correctly when the other side returns a response like this (on other
> >     webservice).
> > 
> >     How can I force the request to have this form?
> > 
> > 
> >     Thanks
> > 
> > 
> >     --
> >     Pedro Alves
> > 
> > 
> 
> -- 
> Pedro Alves
> pedro.alves@zmail.pt
> 
> 
> ------------------------------------------------
> 
> This e-mail, and any attachments thereto, is confidential and is intended only for the
individual(s) named.  If you are not the intended recipient, please let us know by e-mail
reply and delete it from your system; do not copy/save this e-mail or disclose its contents
to anyone.  E-mail transmissions cannot be guaranteed to be secure or error-free as the transmission
could be interrupted, corrupted, lost, destroyed, altered, arrive late or contain viruses.
 ObjectWave does not accept liability for any errors or omissions in the contents of this
e-mail which arise as a result of e-mail transmission.  The views expressed in this e-mail
do not necessarily reflect those of ObjectWave or its affiliates.
> 
> ------------------------------------------------
> 
> 



-- 
Pedro Alves
pedro.alves@zmail.pt


Mime
View raw message