{"id":692,"date":"2006-10-30T16:55:00","date_gmt":"2006-10-31T01:55:00","guid":{"rendered":"http:\/\/www.cloudidentity.com\/blog\/2006\/10\/30\/ws-mtompolicy-published\/"},"modified":"2006-10-30T16:55:00","modified_gmt":"2006-10-31T01:55:00","slug":"ws-mtompolicy-published","status":"publish","type":"post","link":"https:\/\/www.cloudidentity.com\/blog\/2006\/10\/30\/ws-mtompolicy-published\/","title":{"rendered":"WS-MTOMPolicy published"},"content":{"rendered":"

Let’s welcome MTOM Serialization Policy Assertion<\/FONT><\/A>, or WS-MTOMPolicy<\/FONT><\/A> for friends and close relatives \ud83d\ude42<\/P>
\n

As we know, WS-Policy<\/FONT><\/A> provides a generic framework of tremendous expressive power. It is sometimes very useful for very specific domains to provide prescriptive guidance about how certain common features can be expressed in form of assertions. WS-SecurityPolicy<\/FONT><\/A> and WS-RMPolicy<\/FONT><\/A> are two examples of this pattern, they mandate how to express common requirements in their own domains (security and reliability) by defining an assertion syntax and assigning a clear semantic (ie: expected effects on the behavior of the services). <\/P>
\n

For the sake of simplicity, we can say that  WS-MTOMPolicy<\/EM><\/FONT><\/A> describes how your policy should look like if you want to advertise the fact that your web service supports MTOM<\/EM>.<\/P>
\n

The fragment below comes straight from the spec: the text highlighted in yellow represents what is introduced by WS-MTOMPolicy<\/FONT><\/A>.<\/P>
\n


\n

<?<\/SPAN>xml<\/SPAN> <\/SPAN>version<\/SPAN>=<\/SPAN>“1.0<\/SPAN>“ <\/SPAN>encoding<\/SPAN>=<\/SPAN>“utf-8<\/SPAN>“?><\/SPAN><\/SPAN><\/P>
\n

<<\/SPAN>wsdl:definitions<\/SPAN>  <\/SPAN><\/SPAN>targetNamespace<\/SPAN>=<\/SPAN>“example.com<\/SPAN>“ <\/SPAN><\/SPAN><\/P>
\n

                   <\/SPAN><\/SPAN>xmlns:tns<\/SPAN>=<\/SPAN>“example.com<\/SPAN>“  <\/SPAN><\/SPAN><\/SPAN><\/P>
\n

                   <\/SPAN><\/SPAN>xmlns:wsdl<\/SPAN>=<\/SPAN>“http:\/\/schemas.xmlsoap.org\/wsdl\/<\/SPAN>“                     <\/SPAN><\/SPAN><\/SPAN><\/P>
\n

                   <\/SPAN><\/SPAN>xmlns:wsp<\/SPAN>=<\/SPAN>“http:\/\/schemas.xmlsoap.org\/ws\/2004\/09\/policy<\/SPAN>“<\/SPAN><\/P>
\n

                   <\/SPAN><\/SPAN>xmlns:wsoma<\/SPAN>=<\/SPAN>“http:\/\/schemas.xmlsoap.org\/ws\/2004\/09\/policy\/optimizedmimeserialization<\/SPAN>“<\/SPAN> <\/SPAN><\/P>
\n

                   <\/SPAN><\/SPAN>xmlns:wsu<\/SPAN>=<\/SPAN>“http:\/\/docs.oasis-open.org\/wss\/2004\/01\/oasis-200401-wss-wssecurity-utility-1.0.xsd<\/SPAN>“ ><\/SPAN><\/SPAN><\/P>
\n

  <\/SPAN><<\/SPAN>wsp:Policy<\/SPAN> <\/SPAN>wsu:Id<\/SPAN>=<\/SPAN>“MyPolicy<\/SPAN>“ ><\/SPAN><\/SPAN><\/P>
\n

    <\/SPAN><<\/SPAN><\/SPAN>wsoma:OptimizedMimeSerialization<\/SPAN> \/><\/SPAN><\/SPAN><\/P>
\n

    <\/SPAN><!–<\/SPAN> omitted assertions <\/SPAN>–><\/SPAN><\/P>
\n

  <\/SPAN><\/<\/SPAN>wsp:Policy<\/SPAN>><\/SPAN><\/P>
\n

  <\/SPAN><!–<\/SPAN> omitted elements <\/SPAN>–><\/SPAN><\/P>
\n

  <\/SPAN><<\/SPAN>wsdl:binding<\/SPAN> <\/SPAN>name<\/SPAN>=<\/SPAN>“MyBinding<\/SPAN>“ <\/SPAN>type<\/SPAN>=<\/SPAN>“tns:MyPortType<\/SPAN>“ ><\/SPAN><\/SPAN><\/P>
\n

    <\/SPAN><<\/SPAN>wsp:PolicyReference<\/SPAN>  <\/SPAN><\/SPAN>URI<\/SPAN>=<\/SPAN>“#MyPolicy<\/SPAN>“ <\/SPAN>wsdl:required<\/SPAN>=<\/SPAN>“true<\/SPAN>“ \/><\/SPAN><\/SPAN><\/P>
\n

    <\/SPAN><!–<\/SPAN> omitted elements <\/SPAN>–><\/SPAN><\/P>
\n

  <\/SPAN><\/<\/SPAN>wsdl:binding<\/SPAN>><\/SPAN><\/P>
\n

<\/<\/SPAN>wsdl:definitions<\/SPAN>><\/SPAN><\/P><\/DIV>
\n

 <\/P><\/p>\n

<\/div>\n","protected":false},"excerpt":{"rendered":"

Let’s welcome MTOM Serialization Policy Assertion, or WS-MTOMPolicy for friends and close relatives \ud83d\ude42 As we know, WS-Policy provides a generic framework of tremendous expressive power. It is sometimes very useful for very specific domains to provide prescriptive guidance about how certain common features can be expressed in form of assertions. WS-SecurityPolicy and WS-RMPolicy…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"footnotes":""},"categories":[61],"tags":[],"class_list":["post-692","post","type-post","status-publish","format-standard","hentry","category-architecture-ws"],"_links":{"self":[{"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/posts\/692","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/comments?post=692"}],"version-history":[{"count":0,"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/posts\/692\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/media?parent=692"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/categories?post=692"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/tags?post=692"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}