Return-Path: Delivered-To: apmail-xml-axis-user-archive@xml.apache.org Received: (qmail 25365 invoked by uid 500); 2 Jan 2003 18:26:21 -0000 Mailing-List: contact axis-user-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-user@xml.apache.org Received: (qmail 25353 invoked from network); 2 Jan 2003 18:26:21 -0000 Message-ID: <00bc01c2b28c$b032f3d0$1219570f@ranier> From: "Steve Loughran" To: References: <20030102031203.45657.qmail@web11102.mail.yahoo.com> Subject: Re: Interoperability Axis with .NET (C#) Date: Thu, 2 Jan 2003 10:28:01 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-MailScanner: Found to be clean X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ----- Original Message ----- From: "Gene Chuang" To: Sent: Wednesday, January 01, 2003 19:12 Subject: Re: Interoperability Axis with .NET (C#) > > I just created a web service with Axis 1.1beta for a RPC method that returns an array of JavaBeans. > I installed Office XP WS Toolkit 2.0, http://www.microsoft.com/office/developer/webservices/toolkit.asp, and by just supplying the WSDL generated from above, MS VB generated the correct client stubs without my interference. The only caveat is toolkit is not .NET, and the code is not VB.NET, so the JavaBean array was represented as a "variant" in VB, a type that has been deprecated for VB.NET ;-). > However, since the Office XP toolkit 2.0 uses the same soapclient30.dll as .NET platform, I don't see how .NET wouldn't be able to interop just as easily as the toolkit did. .net doesnt use soapclient30.dll, which is part of the MS Soap Toolkit; .NEt has its own implementation(s) of SOAP. So you cant guarantee that just because the native code toolkit works. the .NET one will