Hi,
Using WSE 3.0, I've been trying to host my web service in my windows service
and I get the following error: "WSE802: Unsupported SoapChannelCapabilities
Flags."
An earlier post titled "SoapReceiver.Add" on 11/18/05 mentioned a similar
problem and the response was that you can't specify http as the protocol and
must host the web service in IIS. The whole reason I'm doing this with WSE
3.0 is because it states that you can take your asmx web services and move
them out of IIS:
"Integrated with Visual Studio 2005
WSE 3.0 provides support for ASP.NET Web services to be hosted outside of
IIS for example in Windows services, console applications or even COM+
applications and called with TCP protocol. WSE 3.0 has an extensible
architecture that easily allows alternative protocols to be supported e.g.
UDP or SMTP."
So what's the deal? I'm I not setting something up correctly or have we
been fooled in thinking we could really port our ASP.Net web services out of
IIS? One can reasonably expect HTTP to be involved in communicating with a
web service.
Here's my setup:
address = new Uri("http://localhost:8083/myListenerService");
endpoint = new EndpointReference(address);
SoapReceivers.Add(endpoint, typeof(myMessageServiceClass));
Thanks,
CJF
Erikst - 11 May 2006 12:05 GMT
You are only able to host your webservice outside IIS over TCP. If you want
to host your webservice over HTTP outside IIS you need to implement HTTP as a
custom transport using HTTP.SYS, but this is a very complicated proces.
> Hi,
> Using WSE 3.0, I've been trying to host my web service in my windows service
[quoted text clipped - 26 lines]
> Thanks,
> CJF
Dag Sanna - 20 May 2006 12:26 GMT
Hi CJF!
I have just done what you have tried to do, and its not as complicated
as you might think. The reason is that there is a tutorial guiding you
through it all! Also, you could just copy the code from the tutorial and
get a quick start.
Install the full WSE 3.0 package. The explore the samples that comes
with WSE 3.0 development. You want to look closer at the Advanced, Part
2 - Writing a custom HTTP.SYS transport.
Regards
Dag