1. Just as a person can perform one or more roles in a stage
play, a node can play one or more roles in a SOAP message path. Unfortunately,
the designers of SOAP 1.1 confused the words "actor" and
"role"; they specified that you must identify the roles a node will
play by declaring an actor attribute. They've recognized their mistake, and in
SOAP 1.2 this attribute has been renamed role.
2. Neither SOAP 1.1 nor the BP explicitly prohibits
intermediaries from modifying the contents of the Body element. As a result,
the ultimate receiver has no way of knowing if the application-specific data
has changed somewhere along the message path. SOAP 1.2 reduces this uncertainty
by explicitly prohibiting certain intermediaries, called forwarding
intermediaries, from changing the contents of the Body element and recommending
that all other intermediaries, called active intermediaries, use a header block
to document any changes to the Body element.
3. SOAP 1.2 will replace the SOAPAction header with the
protocol-independent action media type (a parameter to the
"application/soap+xml" MIME type), so dependency on this feature may
result in forward-compatibility problems.
No comments:
Post a Comment