Jans, Please do the following:
1) Use the latest version of axis.
2) Don't use Call.NAMESPACE and Call.setMethodName(...). Instead use:
call.setOperationStyle("rpc");
call.setOperationName(new javax.xml.rpc.namespace.QName
("http://soapinterop.org/";, "echoString"));
3) Look at samples.echo.EchoServiceBindingStub:echoStringArray which
invokes a service with an array.
If you have any problems please send a reply.
Rich Scheuerle
XML & Web Services Development
512-838-5115 (IBM TL 678-5115)
Jens Carlberg
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
> cc:
Sent by: Subject: Re: The client fails decoding
the response
[EMAIL PROTECTED]
iu.se
02/18/2002 03:34
AM
Please respond to
axis-user
R J Scheuerle Jr wrote:
>
> If I have time on Monday I will try and debug this situation.
Any help/hints are appreciated. If I can be of assistance, let me know!
> Are you using the latest version of Axis. There have been some changes
in
> this area.
The tests was done with the alpha3-release. I've been experimenting with
later releases too, but the code I posted doesn't compile directly under
later versions of axis.jar - the Call.NAMESPACE constant seems to have
been removed.
I've since been trying to understand the program that tests various data
types on the echo service, but no good example with all extra fat
removed.
> Thanks
Thank _you_. The Axis package has the potential of being very useful.
--
_/ _/_/_/ _/ _/ _/_/_/ | Jens Carlberg, [EMAIL PROTECTED]
_/ _/ _/_/ _/ _/ | UNIT, Linköpings universitet
_/ _/_/ _/ _/_/ _/ | Tel: +46 13 281758
_/_/ _/_/_/ _/ _/ _/_/_/ | Fax: +46 13 284400
