Hi Chamikara, thanks for your reply. Where is the relatesTo header set?, into Utils.createOutMessageContext(), which is invoked by AbstractInOutSyncMessageReceiver.receive()?
Michele Chamikara Jayalath wrote: > Hi Michele, > > Currently it seems that this does not work if you use the > RawXMLINOutMessageReceiver. The reason is this message receiver setting > the relatesTo addressing header in the response message. When this > message goes to the Dispatching Phase of the second invocation it will > fail saying that it cannot correlate the message with a OperationContext > object. > > Seems like you hv to write ur own message receiver similar to > RawXMLINOutMessageReceiver but which does not set the relatesTo > property. Or do the second invocation using a ServiceClient. > > Chamikara > > > > On 6/6/06, *Michele Mazzucco* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Hi all, > > suppose a system with 3 elements, A, B and C where B provides a in-out > operation. > If A sends a request (fireAndForget of sendRobust) to B, supplying the C > target as well, is it possible for the service to return the result > to C > straight away, that is without creating a ServiceClient object? > > > // This service is provided by B and it is invoked by A > public OMElement foo(OMElement payload) { > // the message context is set > > // process the payload > > // use the replyTo if set by A, otherwise set it by using > // message properties (or some informations included into the > // payload > > return result; > } > > Does the result reach the node C? > > > Thanks in advance, > Michele > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
