Finishing the MSMQ transport provider with the WSE 2.0 release bits

I finally have time to sit down and finish off the MSMQ transport provider using the WSE 2.0 release bits.  There was yet another change between the intirm build I was using and the release bits that caused the transport provider to break.  However, with a few minutes of tweaking this evening, I was able…

4

Namespace change for WSE 2.0

If you haven’t already, you need to read Hervey’s blog entry on Namespaces.  Short summary: the namespace for WSE 2.0 has changed from Microsoft.Web.Services to Microsoft.Web.Services2 … note the all important “2” at the end of the namespace.  This applies to the name of the assembly as well. For me, it means revisiting all of…

0

Refactoring MSMQSoapProvider for Generic Async Support

I had an epiphany the other day in which I realized there’s no need for both the MSMQ and MQSeries channels to have their own, dedicated SoapTransport.  Instead, the transport itself is really quite generic.  It’s the transport-specific channel that we really care about.  Thus, SoapAsyncTransport was born to service the needs of both queuing…

2

Success with SoapMQSeriesChannel

I can proudly report success for the MQSeries channel for WSE 2.0.  At 8:18AM CST, the StockServiceClient was able to invoke the StockService using IBM WebSphere MQ 5.3 as the messaging transport and receive a response. Hopefully Martin will forgive me for plowing through this rather than waiting.  Credit must go to him, though, as…

2

Success with MSMQSoapProvider

I can proudly report success for the MSMQ transport provider for WSE 2.0.  At 4:35PM CST, the StockServiceClient was able to invoke the StockService using MSMQ as the messaging transport and receive a response. We’re using WS-Addressing to facilitate request/response semantics over an asynchronous transport.  Very cool. We should have a working MQSeries transport before…

3

If you build it, will they come?

I’d like to gauge interest beyond the customers I touch each and every day for the ability to do SOAP messaging over messaging oriented middleware.  Specifically, how many of you would use either Microsoft Message Queue or WebSphere MQ as a transport medium for SOAP messages if the capability existed? As Service Oriented Architectures (SOA)…

2

WSE 2.0: SoapService and XmlSerialization

If you cut your teeth building Web services with ASP.NET, then you’ve become quite accustomed to the developer productivity that results from the automatic serialization of types to/from the <soap:Body>.  Simply declare your method to accept and return the data type of choice, and the underlying infrastructure automagically takes care of serialization for you. Unfortunately,…

5