kSOAP .NET interop

Hello @ll,

like many others here i had problems calling methods from a .net webService, because of the microsoft namespace handling. i found some helpful articles it the kSOAP mailing list, but no one could give me a simple solution. searching the web i found a very interessting article on the serverside which helped me out of my kSOAP-.NET-dilemma.

I hope it could help other newbies to spend their time more effective.

greetZ eddy

here we go:

http://www.theserverside.com/resources/article.jsp?l=Systinet-web-services-part-5

----

this is the part i mean:

Default document style with literal encoding

Some Web services frameworks, including MS .NET, generate, by default!

, a document style Web service, using literal encoding. Although the Web service uses document/literal, the .NET framework makes the service appear to be RPC style to .NET clients. This isn't necessarily so for other Web service frameworks, and many users may find it difficult to access the Web service using an RPC style client. So if you're writing an RPC Web service, force your framework to generate the RPC style WSDL.

Example: Use the [SoapRpcService] directive in your MS .NET RPC Web service implementations:

<%@ WebService Language="C#" Class="MSNetStockService" %>using System.Web.Services;using System.Web.Services.Protocols;using System.Web.Services.Description;[SoapRpcService]public class MSNetStockService { [WebMethod] public double getQuote(string symbol) {...

______________________________________________________________________________
38xTestsieger - WEB.DE FreeMail - Deutschlands beste E-Mail
Design-Mails - einfach schoenere E-Mails - http://f.web.de/?mc=021129