{"id":900,"date":"2005-08-18T01:26:00","date_gmt":"2005-08-18T05:26:00","guid":{"rendered":"http:\/\/www.markbaker.ca\/wp\/2005\/08\/18\/bound-by-bindings\/"},"modified":"2005-08-18T01:26:00","modified_gmt":"2005-08-18T05:26:00","slug":"bound-by-bindings","status":"publish","type":"post","link":"http:\/\/www.markbaker.ca\/blog\/2005\/08\/bound-by-bindings\/","title":{"rendered":"Bound by bindings"},"content":{"rendered":"

Here’s a simple question for WS-* advocates; how does one take a SOAP envelope\/infoset\ngenerated by the WS-Addressing SOAP binding<\/a>,\nand send it via the\nSOAP 1.2 default HTTP binding<\/a>?\nShould be trivial, right? Let’s see. Here’s an example envelope (from the WS-A spec);<\/p>\n\n

\n<S:Envelope xmlns:S=\"http:\/\/www.w3.org\/2003\/05\/soap-envelope\"\n           xmlns:wsa=\"http:\/\/www.w3.org\/2005\/08\/addressing\">\n  <S:Header>\n   <wsa:MessageID>http:\/\/example.com\/6B29FC40-CA47-1067-B31D-00DD010662DA<\/wsa:MessageID>\n   <wsa:ReplyTo>\n     <wsa:Address>http:\/\/example.com\/business\/client1<\/wsa:Address>\n   <\/wsa:ReplyTo>\n   <wsa:To>http:\/\/example.com\/fabrikam\/Purchasing<\/wsa:To>\n   <wsa:Action>http:\/\/example.com\/fabrikam\/SubmitPO<\/wsa:Action>\n  <\/S:Header>\n  <S:Body>\n    ...\n  <\/S:Body>\n<\/S:Envelope>\n<\/pre>\n\n
That envelope contains both a wsa:To and wsa:Action header, which are,\nrespectively, where the message is to be sent, and the action that is\nrequested be done.  Now, off in SOAP\/HTTP land, we have a set of properties\nof the default binding which are required in order to construct a SOAP\/HTTP\nmessage.  Amoungst these properties are\nImmediateDestination<\/a> –\n“where the envelope is to be sent” – and then either\nAction<\/a>\nor\nWeb-Method<\/a>\n(or both – who knows?!) which define the – you guessed it – “the action that is\nrequested be done”.  So, you’d think that WS-Addressing would have to define\nhow to populate those properties from a WS-A infoset, ideally as a function of\nthings like wsa:To and wsa:Action.  AFAICT, it doesn’t.<\/p>\n\n
And to think this think got to\nCR<\/em><\/a>?!\nEgads.<\/p>\n\n
The concept of a “SOAP binding” is prima facie broken because it necessarily\nrequires treating underlying protocols as transport protocols, as if the SOAP\nenvelope was actually a SOAP message\n(hint: it isn’t<\/a>).\nWS-Addressing should either a) map the relevant part of its infoset to the property model\nof the default SOAP\/HTTP binding (e.g. wsa:To -> SOAP’s ImmediateDestination), or b) define a\nnew SOAP\/HTTP binding that does the same thing, should problems be found reusing\nthe default binding.<\/p>","protected":false},"excerpt":{"rendered":"Here’s a simple question for WS-* advocates; how does one take a SOAP envelope\/infoset generated by the WS-Addressing SOAP binding, and send it via the SOAP 1.2 default HTTP binding? Should be trivial, right? Let’s see. Here’s an example envelope (from the WS-A spec); <S:Envelope xmlns:S=”http:\/\/www.w3.org\/2003\/05\/soap-envelope” xmlns:wsa=”http:\/\/www.w3.org\/2005\/08\/addressing”> <S:Header> <wsa:MessageID>http:\/\/example.com\/6B29FC40-CA47-1067-B31D-00DD010662DA<\/wsa:MessageID> <wsa:ReplyTo> <wsa:Address>http:\/\/example.com\/business\/client1<\/wsa:Address> <\/wsa:ReplyTo> <wsa:To>http:\/\/example.com\/fabrikam\/Purchasing<\/wsa:To> <wsa:Action>http:\/\/example.com\/fabrikam\/SubmitPO<\/wsa:Action> <\/S:Header> […]","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[26,40],"class_list":["post-900","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-soap","tag-xml"],"_links":{"self":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/900","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/comments?post=900"}],"version-history":[{"count":0,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/900\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/media?parent=900"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/categories?post=900"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/tags?post=900"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}