Archives
-
PDCBoggers ... I'm in
-
Don hints more in Indigo
Well,
-
soap.inproc:// ??
WSE 2.0 introduces some support for HTTP and HTTPS. It also added full support for SOAP based messaging over TCP. If you look real hard you will find an implementation of an Inproc channel to allow sending and receiving messaging SOAP messages within the same process.
-
Setting up WSE inproc messaging
public class MessagingReceiver : SoapReceiver
{
protected override void Receive(Microsoft.Web.Services.SoapEnvelope envelope
{
System.Diagnostics.Debug.WriteLine(
string.Format("Receive: {0}", envelope.OuterXml));
// TODO: Add a more interesting implementation
}
} -
Another suggestion for a PDC BOF session: Web services Orchestration: More than just getting the weather and checking your stocks
Christian Weyer, fellow Frankonian and web services orchestration guru, and myself submitted another suggestion for a BOF session at the PDC. Take a look at the abstract below and vote for it at: http://www.ineta.org/bof/Default.aspx if you're interested.
-
Microsoft talks more about Indigo
Not too long ago, I had some Microsoft employees evading all questions on Indigo. Now they just published the Conference Tracks and Breakout Sessions for the PDC and the word “Indigo” is all over it. I am psyched to find out what it is...
-
BOF session on XQuery (if you like)
Here comes XQuery
-
WSE 2.0 TP Disappointment
I spent some time with the WSE 2.0 Technology Preview today. After going through the sparse(!) documentation I had some hope that I could register an HTTP endpoint and listen with a SoapReceiver ... only to get a NotSupportedException when I try to register the receiver with the following message:
Listening on the HTTP or HTTPS transports is not a supported operation.
Sounds like WSE 2.0 only supports sending via HTTP. Receiving only works with TCP and in-proc. I wonder if someone@microsoft would tell me if this will change once WSE 2.0 goes final or if I have to wait until some other time until I get WSE over HTTP without IIS.
Maybe if I hacked the HttpChannel in .NET Remoting ... now that I discovered how to customize the remoting message format.
For now it's back to hooking WSE into IIS though.