Hi,
The delivery assurance specified by the WS-ReliableMessaging specification,
is only for a particular sequence. If we need to support a scenario where
messages for multiple web services are ordered using WS-RM then we have to
use the same sequence for the entire scenario. If we use the client as you
mentioned
For example:
new SandeshaContext()
call webservice A (at http:/abc.org)
endSequence()
At this point Sandesha will send the TerminateSequence message and the
messages to A will be delivered reliable. endSequence() will return to the
client only in the following two conditions
1. Messages are all delivered and acknowledged
2. Some error and sequence time out.
So if you want to check whether all the messages are delivered correctly,
use the following method
RMReport report = ctx.endSequence();
if!(report.isAllAcked())
throw some error
// /message to A has been delivered already at this point of code?/
new SandeshaContext()
call webservice B (at http:/cde.org)
Thanks,
Jaliya
----- Original Message -----
From: "Benjamin Schmeling" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, November 29, 2005 9:56 AM
Subject: Oneway ws and reliability
Hi,
imagine the scenario, described in the reliable messaging specification.
Now lets assume the webservices are all oneway and the second message goes
to a third endpoint. I know the specification supports only two endpoints,
but is there a possibility to do the following:
1.) call webservice A (at http:/abc.org)
2.) call webservice B (at http:/cde.org)
3.) call webservice C (at http:/abc.org)
I could do this with 3 separate sequences. At every end of one sequence
endSequence() is called in Sandesha. Can I make the conclusion that after
calling endSequence() the message to all webservices in the sequence are
already successfully delivered?
For example:
new SandeshaContext()
call webservice A (at http:/abc.org)
endSequence()
// /message to A has been delivered already at this point of code?/
new SandeshaContext()
call webservice B (at http:/cde.org)
....
...
..
Thanks,
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
