apArrays="true" and take out noWrapped="true".
>
> -wrapArrays is a new option, since Axis 1.3, and maybe it wasn't
> implemented into the ant task (few people need it anyway).
>
> If the above doesn't work, you'd either have to use ant's "
on as the following to be
> generated, use the -wrapArrays option (by default Axis "unwraps" the
> complexType).
>
>
>
> type="transactionHB24:ArrayHB24ILISTA1" />
>
>
>
> Regards,
> Dies
>
>
> Pedro Alves wrote:
&
ver, I'm almost sure that the server will complain about that unknown
ArrayHB24ILISTA1Stub (since I changed the wsdl but only at client side).
Will test it and say if it works
[]
Pedro
On Thu, Mar 09, 2006 at 06:52:26PM +, Pedro Alves wrote:
>
>
> Hum... I dunno abou
s still:
>
>xsi:type="ns2:RequestBeanHB24">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> The other side (a desperately outdated weblogic...) requires a form
w can I force axis to send the request in this form? (even if I have to
change the wsdl).
Thanks
--
Pedro Alves
[EMAIL PROTECTED]
I really cannot tell any differences
Pedro
> > On 3/8/06, Pedro Alves <[EMAIL PROTECTED] > wrote:
> >
> >
> >
> > Hi.
> >
> > I have a wsdl that has this element in the requ
o TRF-190
0
0.00
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 <[EMAIL PROTECTED] > wrote:
>
>
>
&g
..>
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
Hello.
Below is a copy of a message I sent to the BEAs forums. I guess the
"error" is on their side, but I'm posting the message here in case someone
can give me a hint on how to overcome this.
Thanks
__
I'm having problems integrating an error returned by a web
