That is true if your client is C# or VB program. You have greater control. However, if your client is a browser based program written in ASP.NET, you don't seem to have the same kind of control.
_______________________________________________ Waqar Sadiq EDS EIT EASI - Enterprise Consultant MS: H3-4C-22 5400 Legacy Drive Plano, Texas 75024 phone: +01-972-797-8408 (8-837) e-mail: [EMAIL PROTECTED] fax: +01-972-605-4071 _______________________________________________ -----Original Message----- From: Sam Ruby [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 06, 2002 9:11 AM To: [EMAIL PROTECTED] Subject: RE: AXIS/SOAP Interop Test Summary Waqar Sadiq wrote: > > I was wondering if anyone has tested interoperability with .NET for passing > arrays. I had an EJB service which was deployed using axis. The method > required an array of string parameter. When I called it from .NET client, > it defined the array as separate element and referenced it from the method > body. It seems like Axis as well as soap 2.2 do not handle that. The > particular error I got from the server was that no deserializer found for > ref element. We test against a number of implementations, including .Net, and publish the results at http://www.apache.org/~rubys/ApacheClientInterop.html . Page down for Axis. The secret for getting this to work is to define the [SoapRpcMethod] on your methods in .Net. - Sam Ruby
