Hi Malaka, Why do you think that we need a separate synapse level property to enable blocking mode when there is an already provided configuration in the mediator itself? If you need to use the blocking mode of the call mediator in a particular connector, you can release a new version of the respective connector with the change to the configuration. I don't see a strong enough reason to having this kind of a property. Another issue with this kind of a property is that it will become a global setting and affect all the existing mediation flows.
On Mon, May 9, 2016 at 10:58 AM, Malaka Silva <[email protected]> wrote: > Hi, > > Can we finalize this before ESB 5.0.0 beta release please? > > On Wed, Apr 20, 2016 at 9:47 PM, Malaka Silva <[email protected]> wrote: > >> Find my comments, >> >> On Wed, Apr 20, 2016 at 6:12 PM, Akila Ravihansa Perera < >> [email protected]> wrote: >> >>> Hi Malaka, >>> >>> Call mediator already supports "blocking" mode as per [1]. Is it >>> something else that you are looking for? >>> >> Same is what I mentioned in the above example <call blocking="true">. >> >>> >>> Can you explain the requirement to do blocking mode operations in >>> context of connectors? The mediation is paused anyway when using call >>> mediator. >>> >> Call mediation will continue from that point on wards when response comes >> back to ESB. I am referring to the thread behavior. After requests are sent >> to BE thread will be released. When response comes it'll use a different >> thread. >> >> Some use cases are, handling transactions with JMS,(ESB - >> MB guaranteed delivery use cases) implementing sequential execution (When >> throttling is there in apis) with iterator mediator, etc. >> >>> >>> [1] https://docs.wso2.com/display/ESB490/Call+Mediator >>> >>> Thanks. >>> >>> On Wed, Apr 20, 2016 at 5:33 PM, Malaka Silva <[email protected]> wrote: >>> >>>> Hi All, >>>> >>>> Currently in all connectors we are using call mediator almost in every >>>> method. Sometimes there is a requirement to use the call mediator in >>>> blocking mode within connectors. >>>> >>>> If we need to do that we may have to modify the connectors like >>>> following using filter mediator. >>>> >>>> Shall we introduce a property(synapse level) to control this behavior >>>> from ESB 5.0.0? or are there any better solutions? >>>> >>>> <filter source="$ctx:SALESFORCE_BLOCKING" regex="true"> >>>> <then> >>>> <call blocking="true"> >>>> <endpoint> >>>> <default format="soap11"> >>>> <timeout> >>>> <duration>60000</duration> >>>> <responseAction>fault</responseAction> >>>> </timeout> >>>> <suspendOnFailure> >>>> <initialDuration>2000</initialDuration> >>>> >>>> <progressionFactor>1.0</progressionFactor> >>>> <maximumDuration>3000</maximumDuration> >>>> </suspendOnFailure> >>>> </default> >>>> </endpoint> >>>> </call> >>>> </then> >>>> <else> >>>> <call> >>>> <endpoint> >>>> <default format="soap11"> >>>> <timeout> >>>> <duration>60000</duration> >>>> <responseAction>fault</responseAction> >>>> </timeout> >>>> <suspendOnFailure> >>>> <initialDuration>2000</initialDuration> >>>> >>>> <progressionFactor>1.0</progressionFactor> >>>> <maximumDuration>3000</maximumDuration> >>>> </suspendOnFailure> >>>> </default> >>>> </endpoint> >>>> </call> >>>> </else> >>>> </filter> >>>> >>>> Best Regards, >>>> >>>> Malaka Silva >>>> Senior Tech Lead >>>> M: +94 777 219 791 >>>> Tel : 94 11 214 5345 >>>> Fax :94 11 2145300 >>>> Skype : malaka.sampath.silva >>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >>>> Blog : http://mrmalakasilva.blogspot.com/ >>>> >>>> WSO2, Inc. >>>> lean . enterprise . middleware >>>> http://www.wso2.com/ >>>> http://www.wso2.com/about/team/malaka-silva/ >>>> <http://wso2.com/about/team/malaka-silva/> >>>> https://store.wso2.com/store/ >>>> >>>> Save a tree -Conserve nature & Save the world for your future. Print >>>> this email only if it is absolutely necessary. >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> Akila Ravihansa Perera >>> WSO2 Inc.; http://wso2.com/ >>> >>> Blog: http://ravihansa3000.blogspot.com >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> >> Best Regards, >> >> Malaka Silva >> Senior Tech Lead >> M: +94 777 219 791 >> Tel : 94 11 214 5345 >> Fax :94 11 2145300 >> Skype : malaka.sampath.silva >> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >> Blog : http://mrmalakasilva.blogspot.com/ >> >> WSO2, Inc. >> lean . enterprise . middleware >> http://www.wso2.com/ >> http://www.wso2.com/about/team/malaka-silva/ >> <http://wso2.com/about/team/malaka-silva/> >> https://store.wso2.com/store/ >> >> Save a tree -Conserve nature & Save the world for your future. Print this >> email only if it is absolutely necessary. >> > > > > -- > > Best Regards, > > Malaka Silva > Senior Tech Lead > M: +94 777 219 791 > Tel : 94 11 214 5345 > Fax :94 11 2145300 > Skype : malaka.sampath.silva > LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 > Blog : http://mrmalakasilva.blogspot.com/ > > WSO2, Inc. > lean . enterprise . middleware > http://www.wso2.com/ > http://www.wso2.com/about/team/malaka-silva/ > <http://wso2.com/about/team/malaka-silva/> > https://store.wso2.com/store/ > > Save a tree -Conserve nature & Save the world for your future. Print this > email only if it is absolutely necessary. > -- Thank you and Best Regards, Chanaka Fernando Senior Technical Lead WSO2, Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 773337238 Blog : http://soatutorials.blogspot.com LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0 Twitter:https://twitter.com/chanakaudaya
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
