RE: Parsing WSDL and System.Web.Services.Description
From: Elena Kharitidi (elenak_at_online.microsoft.com)
Date: 09/01/04
- Next message: Elena Kharitidi: "Re: Re: System.IO.FileNotFoundException error after splitting one dll into two"
- Previous message: Peter Conrey: "Problem using Perl web service with C# client."
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 01 Sep 2004 18:49:08 GMT
I do not believe that this can be done in the general case: in the case of
Document/literal the schema xs:element referenced by the wsdl:part element
describes the wire format, not the implementation details: the AddStrings
can be a method name with two string parameters:
public string AddStrings(string s1, string s2) {..}
or a method taking Strings instance with parameter style bare
public string Add(Strings AddStrings) {..}
public class Strings {
public string s1;
public string s2;
}
If you do not care of the actual implementation, and just want to present
user with a sample method signature derived from the given WSDL, you would
have to be able to parse all schema constructs and interpret them one way
or other: attributes, nested groups, element references, and so on.
Thanks,
Elena
- Next message: Elena Kharitidi: "Re: Re: System.IO.FileNotFoundException error after splitting one dll into two"
- Previous message: Peter Conrey: "Problem using Perl web service with C# client."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|