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>
<endpoint name="StockQuoteService">
<address uri="
http://localhost:9000/services/SimpleStockQuoteService"/>
</endpoint>
Thanks,
Kathees
On Tue, Feb 24, 2015 at 3:14 PM, Isuru Udana <[email protected]> wrote:
> Hi Kathees,
>
>
>
> On Tue, Feb 24, 2015 at 3:06 PM, Kathees Rajendram <[email protected]>
> 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: [email protected]
>> mobile: +94772596173
>>
>
>
>
> --
> *Isuru Udana*
> Senior
> *Software Engineer*
> WSO2 Inc.; http://wso2.com
> email: [email protected] cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
> twitter: http://twitter.com/isudana
>
--
Kathees
Software Engineer,
email: [email protected]
mobile: +94772596173
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
