|
Replies:
1
-
Last Post:
Feb 6, 2008 8:28 AM
by: haroldcarr
|
|
|
|
|
|
|
How does WS-Reliability ensure messages are not lost in metro?
Posted:
Feb 5, 2008 6:50 PM
|
|
|
Using WS-Reliability for a web service in NetBeans seems to just be a case of turning on a checkbox for the web service. But how is this actually handled by metro? How are SOAP messages over HTTP made reliable?
I would expect that for a reliable solution, the client needs to know how to manage broken HTTP pipes / timeouts and redeliver any WS requests. If the HTTP response is not received by the client, how does the client know whether the message was actually received by the WS or not? One implementation could be for the web service to actually maintain state of these requests and save the results of duplicate requests for specific clients so that they are not replayed.
So, again what does metro do to ensure WS-Reliability?
|
|
|
|
|
|
|
Re: How does WS-Reliability ensure messages are not lost in metro?
Posted:
Feb 6, 2008 8:28 AM
in response to: lpolycarpou
|
|
|
Metro 1.0 and 1.1 implement the WS-ReliableMessaging 1.0 specification which states how the messages are made reliable: https://wsit.dev.java.net/specification-links.html
A future release of Metro will update to WS-ReliableMessaging 1.1.
|
|
|
|
|
java.net RSS
