rodpn

All,

I'm starting to implement a service with WCF and to build it, I have already a WSDL defined by my customer that I have to fit in.

How can I generate the server code for my service, based on WCF, having as my input the WSDL

scvutil.exe won't do it (or at least I didn't find how to do it).

any tips there

Thanks in advance

Rod



Re: Windows Communication Foundation (Indigo) I have the WSDL

stswordman


"svcutil  *.xsd  *.wsdl"

run the "svcutil" to see the help....
you also need  .xsd file









Re: Windows Communication Foundation (Indigo) I have the WSDL

rodpn

Hi there,

Thanks for your reply,

I'm not talking about the proxy code to access the service, but the code to implement the server.

Can I do that with svcutil

Regards

Rdorigo





Re: Windows Communication Foundation (Indigo) I have the WSDL

Brian McNamara - MSFT

No, sorry, there is no tool to do this.

However, after running svcutil, you can discard the generated 'clients', but keep the contracts (service contract, data contract, message contract), and then to implement the service just write a class that implements the service contract interface.






Re: Windows Communication Foundation (Indigo) I have the WSDL

rodpn

Hi Brian,

Thanks for your reply.

If I do exactly what you've said. I use svcutil to generate the contract, data contract and message contract and then I implememnt the service contract and I code everything I need.

When the client application that will use my WCF service (built in JAVA for example based on the WSDL that he gave me) try to access it....will this work transparently

Thanks

rod





Re: Windows Communication Foundation (Indigo) I have the WSDL

Brian McNamara - MSFT

It should.

I forgot to mention the config - svcutil will also generate a config file for the client, which includes the Binding for the client endpoint. You will want to use the same Binding to host the service endpoint (e.g. cut and paste the <endpoint binding=... bindingConfiguration=...> and <bindings> from the svcutil output.config and use it in the server's config).

After that, the server will have the same contracts & binding as in the WSDL, so a client built from the WSDL (WCF or other) should 'just work'.