Well there are several ways to set up the configuration such that a TerminateSequence is sent under ceratin circumstances, for example:
- after a certain number of messages have been sent - when a certain number of messages remain unACKed - when the SequenceAcknowledgement reaches a certain degree of fragmentation into ranges separate by holes in the message stream - on the expiry of an inactivity timeout. We don't really provide a user-oriented programmatic mechanism for forcing termination though. Now you could tarverse the interceptor chain from the proxy, down-cast to the relevant RM interceptor and use the internal APIs to force the termination. However this approach would not be recommended as it is likely to be fragile. There are a number of non-obvious things that need to be done prior to termination in some circumstances, to ensure the best chance of a graceful shutdown. Cheers, Eoghan -----Original Message----- From: fmireaux [mailto:[email protected]] Sent: Wed 18/03/2009 08:40 To: [email protected] Subject: How to terminate a WS-RM sequence ? Using WS-RM, is there a mean for a client to terminate a sequence, like tagging a message as the last message ? -- View this message in context: http://www.nabble.com/How-to-terminate-a-WS-RM-sequence---tp22574670p22574670.html Sent from the cxf-user mailing list archive at Nabble.com.
