This sounds like the appropriate way to handle the scenario IMO too. If we can capture the responses up to the first fault sequence (or let the user to decide whatever the exit condition) and then hit the out sequence with the aggregated responses up to that point, we can cater this behavior. How complex/simple would it be to implement this logic?
Cheers, Pubudu. On Friday, 25 March 2016, Nadeeshaan Gunasinghe <[email protected]> wrote: > Hi Prabath,Pubudu, > > I think Prabath's idea makes sense in this case. If the error occurs we > can hit the fault sequence and then set there a property to track the > message count and then using the loopback mediator we can hit the out > sequence. Then we can respond back to the customer. Shall we try this way? > > Thanks, > > *Nadeeshaan Gunasinghe* > Software Engineer, WSO2 Inc. http://wso2.com > +94770596754 | [email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');> | Skype: > nadeeshaan.gunasinghe <#m_-8879322984164542196_> > <http://www.facebook.com/nadeeshaan.gunasinghe> > <http://lk.linkedin.com/in/nadeeshaan> <http://twitter.com/Nadeeshaan> > <http://nadeeshaan.blogspot.com/> > Get a signature like this: Click here! > <http://ws-promos.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS9lbWFpbC1pbnN0YWxsP3dzX25jaWQ9NjcyMjk0MDA4JnV0bV9zb3VyY2U9ZXh0ZW5zaW9uJnV0bV9tZWRpdW09ZW1haWwmdXRtX2NhbXBhaWduPXByb21vXzU3MzI1Njg1NDg3Njk3OTIiLCAiZSI6ICI1NzMyNTY4NTQ4NzY5NzkyIn0=&u=241407646624225> > > On Fri, Mar 25, 2016 at 10:45 AM, Prabath Ariyarathna <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: > >> Hi All. >> >> In the existing implementation we have max and min number of message >> configuration. When the number of response messages received reaches this >> number, the aggregation will be completed but we don't have way to >> identified the request failure inside the aggregate mediator and break the >> aggregation. If we can add some configuration that can check the status of >> the response to the "completeCondition" block as we done for the >> messageCount, We can overcome this kind of issues I guess. >> WDYT ? >> >> Thanks. >> >> On Fri, Mar 25, 2016 at 10:04 AM, Pubudu Priyashan <[email protected] >> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: >> >>> Hi all, >>> >>> We came across a scenario where the user needs to exit iterate mediator >>> without having to wait for all iterations to be completed. Consider the >>> following scenario. >>> >>> 1. Iterate mediator splits the message into 10 pieces >>> 2. For each message, some operations occur (eg:- update a db record) >>> 3. 6th operation fails >>> >>> The user needs to collect the responses up to 6th iteration and send it >>> back to the client instead of having to wait for all 10 messages to be >>> processed. Currently, we have to use the iterate mediator and wait for all >>> the 10 messages to be processed in order to send back to the client. >>> >>> My suggestion/question is, is it possible to support 'break' statement >>> like functionality to work with iterate mediator? Please provide your >>> feedback and I have created the ticket [1] to track this improvement. >>> Thanks! >>> >>> [1] https://wso2.org/jira/browse/ESBJAVA-4517 >>> >>> Cheers, >>> Pubudu D.P >>> Senior Software Engineer - QA Team | WSO2 inc. >>> Mobile : +94775464547 >>> >> >> >> >> -- >> >> *Prabath Ariyarathna* >> >> *Associate Technical Lead* >> >> *WSO2, Inc. * >> >> *lean . enterprise . middleware * >> >> >> *Email: [email protected] >> <javascript:_e(%7B%7D,'cvml','[email protected]');>* >> >> *Blog: http://prabu-lk.blogspot.com <http://prabu-lk.blogspot.com>* >> >> *Flicker : https://www.flickr.com/photos/47759189@N08 >> <https://www.flickr.com/photos/47759189@N08>* >> >> *Mobile: +94 77 699 4730 * >> >> >> >> >> >> > -- Sent from Gmail Mobile
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
