WS-addressing
-
Hello everyone, Reading the W3 Spec of WS-Addressing is boring. Any recommendations for any easy to read/learn documents/samples? thanks in advance, George
-
Hello everyone, Reading the W3 Spec of WS-Addressing is boring. Any recommendations for any easy to read/learn documents/samples? thanks in advance, George
-
Thanks cpkilekofp, The wiki document is really good. But it is short. :-) Do you have any documents which is more comprehensive than the wiki document, but more readable than the Spec to recommenda? :-) regards, George
-
Thanks cpkilekofp, The wiki document is really good. But it is short. :-) Do you have any documents which is more comprehensive than the wiki document, but more readable than the Spec to recommenda? :-) regards, George
George_George wrote:
The wiki document is really good. But it is short. Do you have any documents which is more comprehensive than the wiki document, but more readable than the Spec to recommenda?
Sadly, at this time I do not. However, I did note that Google produced quite a few documents (the Wikipedia article was simply the first).
-
George_George wrote:
The wiki document is really good. But it is short. Do you have any documents which is more comprehensive than the wiki document, but more readable than the Spec to recommenda?
Sadly, at this time I do not. However, I did note that Google produced quite a few documents (the Wikipedia article was simply the first).
Thanks cpkilekofp, A further question, in the wikipedia page, http://en.wikipedia.org/wiki/WS-Addressing how do you understand "It essentially consists of two parts: a structure for communicating a reference to a Web service endpoint, and a set of Message Addressing Properties which associate addressing information with a particular message."? 1. My confusion is, what means "a structure for communicating a reference to a Web service endpoint"? 2. and what are the so-called "Message Addressing Properties"? Do they mean the To, Action, ReplyAction headers? regards, George
-
Thanks cpkilekofp, A further question, in the wikipedia page, http://en.wikipedia.org/wiki/WS-Addressing how do you understand "It essentially consists of two parts: a structure for communicating a reference to a Web service endpoint, and a set of Message Addressing Properties which associate addressing information with a particular message."? 1. My confusion is, what means "a structure for communicating a reference to a Web service endpoint"? 2. and what are the so-called "Message Addressing Properties"? Do they mean the To, Action, ReplyAction headers? regards, George
George_George wrote:
1. My confusion is, what means "a structure for communicating a reference to a Web service endpoint"? 2. and what are the so-called "Message Addressing Properties"? Do they mean the To, Action, ReplyAction headers?
George, I wish I could tell you off the top of my head. Perhaps some Web Service/SOAP guru will come to your aid at this point (I am NOT that guru); I could figure it out, but I'm in the process of moving to a new position with a government organization and, while I'm introducing my fellow developer to the apps I maintain, the time I can devote to researching answers in topics I don't know that well is quite limited. Sorry, and good luck.
-
George_George wrote:
1. My confusion is, what means "a structure for communicating a reference to a Web service endpoint"? 2. and what are the so-called "Message Addressing Properties"? Do they mean the To, Action, ReplyAction headers?
George, I wish I could tell you off the top of my head. Perhaps some Web Service/SOAP guru will come to your aid at this point (I am NOT that guru); I could figure it out, but I'm in the process of moving to a new position with a government organization and, while I'm introducing my fellow developer to the apps I maintain, the time I can devote to researching answers in topics I don't know that well is quite limited. Sorry, and good luck.
Thanks cpkilekofp! It is fine. Just share when on your demand you feel ok. :-) Anyway, besides this forum, do you have think there is any more specific forums which is more suitable for my web services detailed question? :-) regards, George
-
Thanks cpkilekofp, A further question, in the wikipedia page, http://en.wikipedia.org/wiki/WS-Addressing how do you understand "It essentially consists of two parts: a structure for communicating a reference to a Web service endpoint, and a set of Message Addressing Properties which associate addressing information with a particular message."? 1. My confusion is, what means "a structure for communicating a reference to a Web service endpoint"? 2. and what are the so-called "Message Addressing Properties"? Do they mean the To, Action, ReplyAction headers? regards, George
Hello George, Message Addressing properties are the properties or attributes of a particular WS-Addressing implementation objects. In runtime execution they hold the data in the memory before you serialize them as headers within a SOAP envelope for the "wire" transport. The other way around, the dispatcher of SOAP messages with WSA deserializes the headers' information into runtime objects or properties from the transport protocol. EPR is an XML element of type wsa:EndpointReferenceType. It is a structure which you can use to convey specific endpoint instance information, or just reach particular endpoint or instance of a service endpoint. The ReplyTo, From, FaultTo headers are types of EPR. They bring information how to reach an endpoint in different ways and cases. Best regards, choopie
-
Hello George, Message Addressing properties are the properties or attributes of a particular WS-Addressing implementation objects. In runtime execution they hold the data in the memory before you serialize them as headers within a SOAP envelope for the "wire" transport. The other way around, the dispatcher of SOAP messages with WSA deserializes the headers' information into runtime objects or properties from the transport protocol. EPR is an XML element of type wsa:EndpointReferenceType. It is a structure which you can use to convey specific endpoint instance information, or just reach particular endpoint or instance of a service endpoint. The ReplyTo, From, FaultTo headers are types of EPR. They bring information how to reach an endpoint in different ways and cases. Best regards, choopie
Thanks choopie, 1. Could I understand EPR as URL/URI for an endpoint? 2. "Message Addressing properties are the properties or attributes of a particular WS-Addressing implementation objects." -- I am confused about what do you mean "a particular WS-Addressing implementation objects"? Any other or more words about what do you mean please? 3. "In runtime execution they hold the data in the memory before you serialize them as headers within a SOAP envelope for the "wire" transport." -- do you mean it is our developer's responsibility to generate WS-Address information other than underlying web services stack generates them automatically? :-) regards, George
-
Thanks choopie, 1. Could I understand EPR as URL/URI for an endpoint? 2. "Message Addressing properties are the properties or attributes of a particular WS-Addressing implementation objects." -- I am confused about what do you mean "a particular WS-Addressing implementation objects"? Any other or more words about what do you mean please? 3. "In runtime execution they hold the data in the memory before you serialize them as headers within a SOAP envelope for the "wire" transport." -- do you mean it is our developer's responsibility to generate WS-Address information other than underlying web services stack generates them automatically? :-) regards, George
Hello George, consider EPRs as a way to connect a service endpoint. If you look at some examples you might see ReplyTo header which contains Address, reference parameters or metadata. This means that the client which sends such request to a provider, expects a response to the specified address in the ReplyTo, with supplied reference parameters and maybe some metadata. Like the client, the provider may also offer special communication with endpoint instances. The wsdl contains the information for provider's endpoints. Different bindings could be set for calling endpoints with reference parameters for example. Consider such provider as an EPR itself. The request's wsa:To maps directly to the provider's destination URL. Reference parameters are set directly as separate headers with wsa:IsReferenceParameter attribute set and so on. You need to look for some ws communication with all of the combination and headers in use. You can find a part of the W3C org tests of WS-A here: http://dev.w3.org/2004/ws/addressing/testsuite/testcases/#test1100 Particular implementation means that you can write your own Addressing SOAP feature with any language. You can write it as you like. You can follow the specification or you may not follow everything in the specification, but if you don't, you risk to have not an interopable implementation with third party vendors. Interoperability is a key moment in web service communication. Endpoint address information could be found in the wsdl or some metadata or address of an EPR. If the anonymous client URI is used (SOAP over HTTP) then the Reply is returned on the same HTTP connection. Serialization is transformation from the property data to an XML infoset. Deserialization is the oposite. Best regards, choopie