Arjan Visser wrote: > Paul, > > Yes, that’s exactly what I need! Is this feature on the WSO2 ESB roadmap? > Yes, this will be available soon on the next release.
But, you could do this with a set of callout mediators even now. On a side note do you need the response of the first iteration to go for the next iteration?, I am trying to understand the requirement for the serial iteration... If the above is the case adding a single threaded thread pool will not solve the problem, if it is not that I would like to know the requirement to better support your exact requirement. Thanks, Ruwan > Arjan > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Paul Fremantle > Sent: maandag 23 november 2009 13:44 > To: [email protected] > Subject: Re: [esb-java-user] How to use Axis client in a class mediator > > Rajika/Arjan > > Recently I discussed adding a thread-pool size to the iterate mediator > for exactly this reason - the requirement to have only a single thread > executing. Would that solve your problem? > > Paul > > 2009/11/23 Arjan Visser <[email protected]>: > >> A callout mediator works for just 1 call. I need to do a number of calls >> > in > >> sequence. Also iterator does not work because it processes all calls in >> parallel. What I need is a serial iterator. >> >> >> >> For every <article> in <articles> I need to do a SOAP call in sequence. >> > How > >> to implement this in the bus? >> >> >> >> <articles> >> >> <article>ID1</article> >> >> <article>ID2</article> >> >> <article>ID2</article> >> >> </articles> >> >> >> >> >> >> >> >> ________________________________ >> >> From: [email protected] >> > [mailto:[email protected]] > >> On Behalf Of Rajika Kumarasiri >> Sent: maandag 23 november 2009 12:53 >> To: [email protected] >> Subject: Re: [esb-java-user] How to use Axis client in a class mediator >> >> >> >> >> >> On Mon, Nov 23, 2009 at 3:49 PM, Arjan Visser <[email protected]> >> wrote: >> Try using callout mediator. >> >> Rajika >> >> Hi, >> >> >> >> I have to use Axis2 client in a class mediator for calling an external >> webservice. This call has to be a blocking call. When I use this client in >> the class mediator, I get the following error: >> >> >> >> 2009-11-23 11:08:23,015 [-] [HttpClientWorker-8] ERROR AxisEngine Message >> Receiver not found for AxisOperation: {http://ws.apach >> >> }anonOutInOp >> >> org.apache.axis2.AxisFault: Message Receiver not found for AxisOperation: >> {http://ws.apache.org/namespaces/axis2}anonOutInOp >> >> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:174) >> >> at >> org.apache.synapse.transport.nhttp.ClientWorker.run(ClientWorker.java:229) >> >> at >> >> > org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerP > ool.java:58) > >> at >> >> > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.ja > va:886) > >> at >> >> > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:9 > 08) > >> at java.lang.Thread.run(Thread.java:619) >> >> >> >> What is the right way to use a blocking SOAP call in a mediator? Using the >> same class mediator in a standalone Java projects works fine (using the >> Axis2 libraries packed with WSO2). >> >> >> >> Used version : 2.1.2 >> >> >> >> Arjan >> >> _______________________________________________ >> Esb-java-user mailing list >> [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 Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: [email protected]; cell: +94 77 341 3097 blog: http://blog.ruwan.org _______________________________________________ Esb-java-user mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
