Hi Isuru, I have implemented the blocking functionality in call mediator.
Please find the pull request [1] for wso2-synapse [1] - https://github.com/wso2/wso2-synapse/pull/93 Thanks, Kathees On Wed, Feb 25, 2015 at 5:06 PM, Kathees Rajendram <kath...@wso2.com> wrote: > Hi Isuru, > > Endpoint with key is not handled in BlockingSender.I will introduce the > changes in BlockingSender. > > Thanks, > kathees > > On Wed, Feb 25, 2015 at 4:26 PM, Isuru Udana <isu...@wso2.com> wrote: > >> Hi Kathees, >> >> If you find this not working, please introduce this change to the >> BlockingMsgSender but not the Call Mediator. So that all the components >> using BlockingMsgSender will inherit this. >> >> Thanks. >> >> >> On Wed, Feb 25, 2015 at 4:14 PM, Isuru Udana <isu...@wso2.com> wrote: >> >>> Hi Kathees, >>> >>> On Tue, Feb 24, 2015 at 4:00 PM, Kathees Rajendram <kath...@wso2.com> >>> wrote: >>> >>>> Hi Isuru, >>>> >>>> The blocking is working in the following synapse configuration. >>>> >>>> <call blocking="true"> >>>> <endpoint name="StockQuoteService"> >>>> <address uri=" >>>> http://localhost:9000/services/SimpleStockQuoteService"/> >>>> </endpoint> >>>> </call> >>>> >>>> but I want to add the blocking in the following configuration also, as >>>> it is in call mediator. >>>> >>>> <call blocking="true"> >>>> <endpoint key="StockQuoteService"/> >>>> </call> >>>> >>> I do not think you need to explicitly handle this. AFAIR >>> BlockingMsgSender handles the IndirectEndpoint so no extra work needed. >>> >> >>> Thanks. >>> >>>> >>>> >>>> <endpoint name="StockQuoteService"> >>>> <address uri=" >>>> http://localhost:9000/services/SimpleStockQuoteService"/> >>>> </endpoint> >>>> >>>> >>>> Thanks, >>>> Kathees >>>> >>>> >>>> On Tue, Feb 24, 2015 at 3:14 PM, Isuru Udana <isu...@wso2.com> wrote: >>>> >>>>> Hi Kathees, >>>>> >>>>> >>>>> >>>>> On Tue, Feb 24, 2015 at 3:06 PM, Kathees Rajendram <kath...@wso2.com> >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> The call mediator blocking is working with direct endpoint. I want to >>>>>> write logic with endpoint key and Xpath. We can't use the existing >>>>>> functionality for blocking as it is in call mediator. >>>>>> >>>>> Could you please clarify what you mean by xpath here ? >>>>> If you meant getting Source/Target xpath expressions in Callout >>>>> mediator options into Call mediator, that is not required at all. Same for >>>>> the endpoint key as well. >>>>> Let's stick to the above discussed configuration syntax and >>>>> functionality. >>>>> >>>>> Thanks. >>>>> >>>>> >>>>>> >>>>>> Thanks, >>>>>> Kathees >>>>>> -- >>>>>> Kathees >>>>>> Software Engineer, >>>>>> email: kath...@wso2.com >>>>>> mobile: +94772596173 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> *Isuru Udana* >>>>> Senior >>>>> *Software Engineer* >>>>> WSO2 Inc.; http://wso2.com >>>>> email: isu...@wso2.com cell: +94 77 3791887 >>>>> blog: http://mytecheye.blogspot.com/ >>>>> twitter: http://twitter.com/isudana >>>>> >>>> >>>> >>>> >>>> -- >>>> Kathees >>>> Software Engineer, >>>> email: kath...@wso2.com >>>> mobile: +94772596173 >>>> >>> >>> >>> >>> -- >>> *Isuru Udana* >>> Senior >>> *Software Engineer* >>> WSO2 Inc.; http://wso2.com >>> email: isu...@wso2.com cell: +94 77 3791887 >>> blog: http://mytecheye.blogspot.com/ >>> twitter: http://twitter.com/isudana >>> >> >> >> >> -- >> *Isuru Udana* >> Senior >> *Software Engineer* >> WSO2 Inc.; http://wso2.com >> email: isu...@wso2.com cell: +94 77 3791887 >> blog: http://mytecheye.blogspot.com/ >> twitter: http://twitter.com/isudana >> > > > > -- > Kathees > Software Engineer, > email: kath...@wso2.com > mobile: +94772596173 > -- Kathees Software Engineer, email: kath...@wso2.com mobile: +94772596173
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
