Harm Verhagen wrote: > harm wrote: > > > 1- receive soap request A. > > > 2 issue external call to externalserver 1. (1 > > > parameter extraction from request A) > > > 3 issue external call to externalserver 2. (1 > > > parameter extraction from request A, 1 parameter based on > > response of > > > externalserver 1) > > > 4 issue external call to externalserver 3. (1 > > > parameter extraction from request A, 2 parameters based on > response > > > of both 1 + 2) > > > 5 assembly response (with params from 1 + 2 + 3 ) > > > 6 send response back to caller. > > One more question > What if in step 5 I need the original message ? > I was thinking about clone/aggregate but not was 100% sure. > Any thoughts ? You could of course do a clone and aggregate but it is more straight forward if you can design the transformations and the attaching part of the responses to the callouts in away that it preserves the original message but just keep on adding content to the message in the 3 callouts...
When doing the transformations to the callout you can prepare part of the message envelop as the pay load for the callout request and it can be specified to the callout mediator using the source element in the configuration. Please have a look at the callout mediator configuration guide. [2] Thanks, Ruwan [2] - http://wso2.org/project/esb/java/2.0.2/docs/configuration_language.html#callout > > Regards, > Harm > > > > On Fri, Apr 3, 2009 at 9:30 AM, Ruwan Linton <[email protected] > <mailto:[email protected]>> wrote: > > Harm Verhagen wrote: > > Ok, Works like a charm > Cool.... Nice to hear you got it to work. :-) > > Thanks, > Ruwan > > Thanks ! > > > > On Fri, Apr 3, 2009 at 6:00 AM, Ruwan Linton <[email protected] > <mailto:[email protected]> > > <mailto:[email protected] <mailto:[email protected]>>> wrote: > > > > Hi Harm, > > > > This is a straight forward case for the callout mediator, please > > have a > > look at the callout mediator sample [1] and in this particular > > case you > > need to have three callout mediators with probably three or > more xslt > > mediators to implement this scenario. > > > > Thanks, > > Ruwan > > > > [1] - > > > > http://wso2.org/project/esb/java/2.0.1/docs/wso2esb-2.0.1-docs/samples/advanced_mediation_samples.html#Callout > > > > Harm Verhagen wrote: > > > My previous mail got out before it was finished. > > > > > > > > > Hi folks, > > > > > > We're struggling with a scenario where an ESB should be very > > helpfull. > > > > > > How can the following beeing achieved ? > > > 1- receive soap request A. > > > 2 issue external call to externalserver > 1. (1 > > > parameter extraction from request A) > > > 3 issue external call to externalserver 2. (1 > > > parameter extraction from request A, 1 parameter based on > > response of > > > externalserver 1) > > > 4 issue external call to externalserver 3. (1 > > > parameter extraction from request A, 2 parameters based > on response > > > of both 1 + 2) > > > 5 assembly response (with params from 1 + 2 + 3 ) > > > 6 send response back to caller. > > > > > > We have been struggling with a single sequence consisting of > > multiple > > > xlst transformations and multiple endpoints. But that > proved to be a > > > PITA. (due to the many unforseen responses from all the > external > > > server 1,2,3) > > > > > > Do you have an advice ? > > > > > > Regards, > > > Harm > > > > > > > > > ------------------------------------------------------------------------ > > > > > > _______________________________________________ > > > Esb-java-user mailing list > > > [email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>> > > > https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user > > > > > > > > > -- > > Ruwan Linton > > Senior Software Engineer & Product Manager; WSO2 ESB; > > http://wso2.org/esb > > WSO2 <http://wso2.org/esb%0AWSO2> Inc.; http://wso2.org > > email: [email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>>; cell: +94 77 341 3097 > > blog: http://ruwansblog.blogspot.com > > > > > > _______________________________________________ > > Esb-java-user mailing list > > [email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>> > > https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user > > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Esb-java-user mailing list > > [email protected] <mailto:[email protected]> > > https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user > > > > > -- > Ruwan Linton > Senior Software Engineer & Product Manager; WSO2 ESB; > http://wso2.org/esb > WSO2 <http://wso2.org/esb%0AWSO2> Inc.; http://wso2.org > email: [email protected] <mailto:[email protected]>; cell: +94 77 341 3097 > blog: http://ruwansblog.blogspot.com > > > _______________________________________________ > Esb-java-user mailing list > [email protected] <mailto:[email protected]> > https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user > > > ------------------------------------------------------------------------ > > _______________________________________________ > Esb-java-user mailing list > [email protected] > https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user > -- Ruwan Linton Senior Software Engineer & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: [email protected]; cell: +94 77 341 3097 blog: http://ruwansblog.blogspot.com _______________________________________________ Esb-java-user mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
