axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pedro Alves <pe...@neraka.no-ip.org>
Subject Re: <item> in Arrays
Date Wed, 08 Mar 2006 15:13:38 GMT
On Wed, Mar 08, 2006 at 09:23:25AM -0500, Anne Thomas Manes wrote:
> What is the type definition for transactionHB24:ArrayHB24ILISTA1?
> 
> Anne

Here is the definition:

      <complexType name="ArrayHB24ILISTA1">
        <sequence>
          <element name="ACCAO" nillable="true" type="string" />
          <element name="CTCANAL_L" nillable="true" type="string" />
          <element name="CKNUMCTA" nillable="true" type="string" />
          <element name="MAXMOV" nillable="true" type="string" />
          <element name="ZORDEM3_L" nillable="true" type="string" />
          <element name="CKBALCAO" nillable="true" type="string" />
          <element name="DESCR1" nillable="true" type="string" />
          <element name="IVISIVEL" nillable="true" type="string" />
          <element name="CPRODMISL" nillable="true" type="string" />
        </sequence>
      </complexType>


As far as I know, axis is doing the right thing - I use it on the client
side. The server is a weblogic 6.1 server.

On another webservice, the response from the server is: (ArrayHB24ILISTA1
is similar to the one I wrote above)

          <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>

Axis can handle this response ok, so thats why I hope to have some kind of
engine option to allow me form a request like this.


Thanks for the help!


> 
> 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

Mime
View raw message