I think what we're mainly missing is a way to brige an InOut with an InOnly meps. That way, your InOut "in" message would be translated to an InOnly, splitted, aggregated, and the response would become the "out" of the original InOut. This pattern is of real need, but noone had found any time to write it ... I don't think using InOut would work, as it has very special meanings for Faults, errors, etc...
On 7/10/07, netflexity <[EMAIL PROTECTED]> wrote:
I have a request message with a list of IDs, which I need to split and invoke service for each given ID. I would want a response to contain a list of all execution results/faults. The only reason I need everything InOut is to be able to return SOAP Response during the same http session, instead of invoking some callback service. Thanks. -Max gnodet wrote: > > Could you please explain how you handle the different messages for an > InOut pattern ? Especially for the splitter / aggregators, I don't really > understand how you can do that using InOut meps... > > On 7/9/07, netflexity <[EMAIL PROTECTED]> wrote: >> >> All my use cases receive SOAP requests and supposed to return SOAP >> responses >> during the same session. HTTP consumer with In-Out MEP does that very >> good. >> But the problem is that I am stuck only with content-based router and >> static >> routing slip, that's is it!!! But I need enricher, which I had to >> re-write >> to in-out and splitter+aggregator. Please advise why things are in-only. >> -- >> View this message in context: >> http://www.nabble.com/Why-all-useful-EIP-are-In-only--tf4049249s12049.html#a11501569 >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Principal Engineer, IONA > Blog: http://gnodet.blogspot.com/ > > -- View this message in context: http://www.nabble.com/Why-all-useful-EIP-are-In-only--tf4049249s12049.html#a11529305 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet ------------------------ Principal Engineer, IONA Blog: http://gnodet.blogspot.com/
