On Wed, 2006-05-31 at 22:29 +0100, David Illsley wrote: > I'll give it a go... > > It is possible to use ws-addressing to do more interesting redirections > than redirection to an async callback address > e.g. 1. use the ReplyTo to invoke a one-way service with the reply > 2. use a FaultTo to redirect faults to a 'collector' service to > monitor failures in you application > > In these cases the services invoked by the reply/fault messages (including > a RelatesTo) may not be connected in any way to the webservies client > which originally set the MessageID and so stand no chance of recognising > it. > > Is that any clearer?
Um no :(. The use of relates to has nothing to do with async in my mind: its just a way to find an old message context and find the related operation context. We don't care (at that time) whether that's used for async correlation or counting potatoes. However, if a relatesTo messageID is not found, that smells like rotten fish to me: that means you sent my engine a message saying "hey I'm related to this other message I (or someone else) sent earlier" and I find that that's not the case. IMO that should raise a fault. If you want to you can always override and replace this dispatcher. We're talking about the default behavior. Sanjiva. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
