L.S., I guess you're now using a routing slip to first do the xslt transformation and then invoke the remote service. To transform the response message, you can just add one extra step to that routing slip with the extra transformation. The out message from the remote service will then be used as the in message for the final transformation and you can create the final response message that way.
Regards, Gert Vanthienen ------------------------ Open Source SOA: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ 2009/12/1 colin.chi <[email protected]>: > > Now, I would like to achieve an in-out MEP calls, and my workflow is as > follows: > > in-out MEP has two steps: > first, external client send a request to smx, then smx transform request, > last send transformed request to external server. > [external client] --> cxf-consumer-su --> eip-su --> saxon-xslt-su --> > cxf-provider-su -->[external server] > -- transform client > request -- > | message to the > message | > -- which server can > read -- > > second, external server reply a response to smx, and smx reply the response > to external client. > > now, we also need to transform response to the message which external client > can read. > > In SMX, I find it is difficult to do that transform response. > > Am i right? Or, if I was wrong, which su or bc can implement. > -- > View this message in context: > http://old.nabble.com/I-have-a-problem-about-message-transform-tp26588084p26588084.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > >
