This is a transport question, and has such, it is not covered by soap. We are using JMS to solve those problems. From the tests we've done, it works has advertised. We still need to test more thought.
But it seems like the weay to get ride of delivery problems. :-) Le mardi 31 Août 2004 16:09, Jeremy Nix a écrit : > This question is more directed at the Webservices in general, as opposed > to Axis, but since I'm using Axis as the wrapper for my web service, it > seemed like a good place to start. I'm relatively new to Axis/Soap, so > if the answer is trivial, I apologize. > > We've created XML services in the past to deal with B2B communications > outside the realm of Soap and WSDL. Using plain HTTP and XML as the > architecture, we were forced to create callbacks on both sides > (client/server) to make sure that messages were received. > > Example: > -Client A sends XML request to Server B > -Server B sends back XML acknowledgement of request to Client A > -Server B sends XML request to Client A with actual response > -Client A sends back XML acknowledgement of request to Server A > > This was our way of dealing with the HTTP protocol in a manner that > guarantees the delivery of messages. > > Does Soap/WSDL/Axis guarantee the delivery of messages? If so, how? > > _________________________________ > Jeremy Nix > Senior Application Developer > Southwest Financial Services, LTD. > (513) 621-6699 x1158 > www.sfsltd.com
