About Question enthuware.ocejws.v6.2.63 :

Moderators: Site Manager, fjwalraven

Post Reply
Posts: 6
Joined: Sat Sep 17, 2016 2:29 am

About Question enthuware.ocejws.v6.2.63 :

Post by vini_srcna »

SOAP v1.1 The SOAP actor global attribute can be used to indicate the recipient of a header element. The value of the SOAP actor attribute is a URI. The special URI "http://schemas.xmlsoap.org/soap/actor/next" indicates that the header element is intended for the very first SOAP application that processes the message. This is similar to the hop-by-hop scope model represented by the Connection header field in HTTP. Not all parts of a SOAP message may be intended for the ultimate destination of the SOAP message but, instead, may be intended for one or more of the intermediaries on the message path. The role of a recipient of a header element is similar to that of accepting a contract in that it cannot be extended beyond the recipient. That is, a recipient receiving a header element MUST NOT forward that header element to the next application in the SOAP message path. The recipient MAY insert a similar header element but in that case, the contract is between that application and the recipient of that header element. In other words: if the role of the actor is "http://schemas.xmlsoap.org/soap/actor/next" it should process the header and remove the header element. It might re-insert a similar header depending on the application
what happens if the receiver is ultimate receiver ?. The intermediaries will process the header, but not remove ?. (or is it like the intermediary node will remove all of the headers, inserts headers intended for ultimate reciever + headers that it could not processs ? )

Posts: 429
Joined: Tue Jul 24, 2012 2:43 am

Re: About Question enthuware.ocejws.v6.2.63 :

Post by fjwalraven »

what happens if the receiver is ultimate receiver ?. The intermediaries will process the header, but not remove ?
If the URI reflects the ultimate receiver (I mean, not having a URI of "http://schemas.xmlsoap.org/soap/actor/next") intermediary nodes wil leave the header untouched and forward it to the next node on the path until it reaches the ultimate receiver (the one with the corresponding URI). The ultimate receiver will then process the header.

Does this answer your question?


Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests