Mark Baker asks how WS-Addressing and the SOAP 1.2 default HTTP binding might work together because of the usual confusion about the roles of and relations between wsa:Action, wsa:To, ImmediateDestination, WebMethod, Action, and HTTP address and headers; Jim Webber partly agrees, but believes viewing HTTP as a transport protocol (which both agree it isn’t) is the right thing to do.
Since I last wrote about this some time ago, I’ve changed my mind a little. For better or for worse, I no longer believe that the WS-* stack can be mapped cleanly to the Web Architecture (read: REST/HTTP); if you’re going down the WS-* road, you just have to view HTTP as a transport — I no longer believe there’s a way to integrate the two approaches.
I also believe that for a majority of use cases, the REST approach is superior. I guess that means Mark can put another notch in his belt …
Cheers, buddy. 8-)