Web Service from WSDL

[CJF]

Is there a way to build a web service from an existing wsdl? I do not wish to
create a .Net web service client proxy from a wsdl, but an actual web
service. I tried using the wsdl.exe utility, but the output is class of type
SoapHttpClientProtocol and not WebService. It was my understanding that you
could create both client proxies and web services from an existing wsdl file?
If not, what's another way of creating a .NET web service that supports the
existing wsdl? I'm using VS 2005.

Thanks,
CJF

[Zdenek Drlik]

CJF napsal(a):

Is there a way to build a web service from an existing wsdl? I do not wish to
create a .Net web service client proxy from a wsdl, but an actual web
service. I tried using the wsdl.exe utility, but the output is class of type
SoapHttpClientProtocol and not WebService. It was my understanding that you
could create both client proxies and web services from an existing wsdl file?
If not, what's another way of creating a .NET web service that supports the
existing wsdl? I'm using VS 2005.

Thanks,
CJF

Using wsdl.exe with "/server" parametr doesn't work? I didn't try it
yet, but documentation says :

/server
Generate an abstract class for an xml web service implementation using
ASP.NET based on the contracts. The default is to generate client proxy
classes.
Zdenek Drlik, MCP

[Zdenek Drlik]

CJF napsal(a):

Is there a way to build a web service from an existing wsdl? I do not wish to
create a .Net web service client proxy from a wsdl, but an actual web
service. I tried using the wsdl.exe utility, but the output is class of type
SoapHttpClientProtocol and not WebService. It was my understanding that you
could create both client proxies and web services from an existing wsdl file?
If not, what's another way of creating a .NET web service that supports the
existing wsdl? I'm using VS 2005.

Thanks,
CJF

The /server switch works in VS 2003' wsdl.exe. VS2005's wsdl.exe has
"/serverInterface" parameter instead.

Zdenek Drlik, MCP

[CJF]

I did run it with the /serverInterface option. I guess I'm suppossed to
create my own web service that implements the interface. Though, my concern
is the wsdl file generated by my .NET web service doesn't match the wsdl file
used to create the interface. I'm unsure as to what the implications are for
clients that use the original wsdl file as oppossed to the wsdl created by my
service. Why are the wsdl files different to begin with? Thanks.

"Zdenek Drlik" wrote:

CJF napsal(a):

Is there a way to build a web service from an existing wsdl? I do not wish to
create a .Net web service client proxy from a wsdl, but an actual web
service. I tried using the wsdl.exe utility, but the output is class of type
SoapHttpClientProtocol and not WebService. It was my understanding that you
could create both client proxies and web services from an existing wsdl file?
If not, what's another way of creating a .NET web service that supports the
existing wsdl? I'm using VS 2005.

Thanks,
CJF

The /server switch works in VS 2003' wsdl.exe. VS2005's wsdl.exe has
"/serverInterface" parameter instead.

Zdenek Drlik, MCP