aspose file tools*
The moose likes Web Services and the fly likes hop-by-hop contract between a SOAP node and the next SOAP Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Web Services
Bookmark "hop-by-hop contract between a SOAP node and the next SOAP" Watch "hop-by-hop contract between a SOAP node and the next SOAP" New topic
Author

hop-by-hop contract between a SOAP node and the next SOAP

Dan Drillich
Ranch Hand

Joined: Jul 09, 2001
Posts: 1164
Good Day,

SOAP, for some reason empathizes the multi-hop paradigm. I don't really understand its importance. Any thoughts?

For example, SOAP Message Transmission Optimization Mechanism says -
Use of the Abstract SOAP Transmission Optimization Feature is a hop-by-hop contract between a SOAP node and the next SOAP node in the SOAP message path, providing no mandatory convention for optimization of SOAP transmission through intermediaries.


Regards,
Dan


William Butler Yeats: All life is a preparation for something that probably will never happen. Unless you make it happen.
Jimmy Clark
Ranch Hand

Joined: Apr 16, 2008
Posts: 2187
A SOAP message can be passed along to a variety of intermediary systems before arriving at its final destination. The importance of this is to not restrict or limit the processing of a SOAP message to a strict point-to-point communication path.
R Srini
Ranch Hand

Joined: Feb 19, 2010
Posts: 215
I was looking at some examples of WS-Addressing at Javapassion and I see where its used to specify the next node to hop to using wsa:To. Is there is different place/standard to specify all of the hops for a given soap message, e.g. is there something like this:

<hops>
<hop sequence="1" address="http://address1" />
<hop sequence="2" address="http://address2" />
<hop sequence="3" address="smtp://address3" />
<hop sequence="4" address="someotherprotocol://address4" />
</hops>

just made that up

Is there a standard for this? Or is this provider-specific, i.e. the way to do it is different for Sun and IBM (for example)?

Thanks!
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: hop-by-hop contract between a SOAP node and the next SOAP
 
Similar Threads
Clarification on mustUnderstand and role attributes of SOAP header blocks
Axis SOAP Web Service with Attachments
unable to understand how to use actor or role SOAP Header attribute
Does MTOM support SOAP 1.2?
Regarding SOAP header relay attribute