Databases
StackOverflow2013
Postsdbo
POGenerate WSDL / SOAP specification from C# Interface as client?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGenerate WSDL / SOAP specification from C# Interface as client?
    primarykey
    data
    text
    <p>Here's my situation: I'm writing a SOAP client using WCF. I am going to invite 3rd parties to develop services that my client can consume. This is kind of backwards from the norm, I think. As the client develper, I'm creating the specification, and the server developers are following it.</p> <p>When it's the other way around, and the server developer is using C#/.NET, the process would go something like:</p> <p>1) Service developer creates C# interface, a service type that implements it, and a host to serve it. 2) Service developer uses its server to generate WSDL and provides it to client developer. 3) Client developer uses WSDL document to generate a proxy and uses the proxy to consume the service.</p> <p>However, I'm completely at a loss as to how to do this in reverse. So far, the only thing I've been able to thing of is to do step 1 as a mock, generate the WSDL for my mock, and provide it to the service developer. I'd prefer not to have to go through the work of doing this. Plus, I'm not sure how feasible it is for the service developer to generate a service based on a a WSDL document, especially since the service developers would probably not be using .NET. They could be using any number of SOAP frameworks and languages. I'm afraid that their service implementations would end up differing enough that my client application wouldn't be compatible with all of them at the same time.</p> <p>I want this to be as easy as possible for the service developers, to encourage them to write them, but I want to have a single client, without having to modify my client code for each server.</p> <p>I'm not really familiar with SOAP frameworks, other than WCF, so I don't really know how much is the same/different from WCF implementation.</p> <p>Ideally, I'd like to just provide them with the C# interfaces, or run them through some tool that would generate information that they can use to implement their services in their language/framework of choice, and perfectly implement my specification.</p> <p>What would be the best way to accomplish this?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USJoeMjr2
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COWhy don't you create a sample service for that client instead? Then you can export the WSDL from that service and also have a working example for testing purposes.
      singulars
      1. POGenerate WSDL / SOAP specification from C# Interface as client?
      1. USReza Sadr
    2. COI did already think of that. I'm just not sure how easy/feasable it is to write a service based on a WSDL document, particularly if it's another language (not .net/wcf). Are there generally tools available to generate service code stubs from WSDL, like there are for clients?
      singulars
      1. POGenerate WSDL / SOAP specification from C# Interface as client?
      1. USJoeMjr2
    3. CO1. WSDLs are language-agnostic. It's the WSDL that exposes the service's metadata in a format that (nearly) any language can understand. 2. A client should not dictate the implementation of the service - the client should consume a WSDL which will tell it everything it needs to know to communicate with the service. An instance of a client (proxy) is specific to an instance of a service - it sounds almost like you want to make a generic client that communicate with any service. Can you give a more concrete example of what you're trying to achieve?
      singulars
      1. POGenerate WSDL / SOAP specification from C# Interface as client?
      1. USTim
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload