Hi,
I am in the progress of implementing the blocking functionality in call
mediator. Now the call mediator synapse syntax is changed to cater the
above requirement.
The synapse configuration for the call mediator blocking functionality
(blocking="true")
<call blocking="true">
<endpoint name="StockQuoteService">
<address uri="http://localhost:9000/services/SimpleStockQuoteService
"/>
</endpoint>
</call>
The synapse configuration for call mediator default functionality
(blocking="false")
<call blocking="false">
<endpoint name="StockQuoteService">
<address uri="http://localhost:9000/services/SimpleStockQuoteService
"/>
</endpoint>
</call>
Since the default behavior of the call mediator is non blocking
functionality, existing configuration will work as it is.
<call>
<endpoint name="StockQuoteService">
<address uri="http://localhost:9000/services/SimpleStockQuoteService
"/>
</endpoint>
</call>
Thanks,
Kathees
On Mon, Feb 16, 2015 at 4:46 PM, Kathees Rajendram <[email protected]> wrote:
> Hi,
>
> We are working on the supporting the blocking functionality in Call
> mediator. In the Call mediator synapse configuration,We are introducing a
> new attribute (blocking="true/false").
>
> New Syntax for Call mediator:
>
> <call [blocking="true|false"]>
> (endpointref | endpoint)+
> </call>
>
> endpointsref refers to the following,
> <endpoint key="name"/>
>
> If the blocking is true, Callout mediator blocking functionality will be
> executed otherwise Call mediator existing functionality will be executed.
>
> Thanks,
> Kathees
>
> On Wed, Nov 19, 2014 at 12:07 PM, Srinath Perera <[email protected]> wrote:
>
>> +1
>>
>> On Wed, Nov 19, 2014 at 11:27 AM, Kasun Indrasiri <[email protected]> wrote:
>>
>>> Hi,
>>>
>>> At the moment 'Call' mediator offers a blocking messaging behavior on
>>> top of non-blocking architecture (i.e. - Request and responses are handled
>>> in different threads). However, there are requirements where we need to
>>> support pure blocking messaging such as JMS transaction scenarios (which we
>>> use Callout mediator at the moment). However, having 'Call' and 'Callout'
>>> mediators is very confusing for the users and we need to have a single
>>> mediator with both capabilities. Hence we can add the blocking support as
>>> part of the Call mediator and deprecate Callout mediator.
>>>
>>> Thanks,
>>>
>>>
>>> --
>>> Kasun Indrasiri
>>> Software Architect
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 77 556 5206
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>> _______________________________________________
>>> Architecture mailing list
>>> [email protected]
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> ============================
>> Srinath Perera, Ph.D.
>> http://people.apache.org/~hemapani/
>> http://srinathsview.blogspot.com/
>>
>> _______________________________________________
>> Architecture mailing list
>> [email protected]
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Kathees
> Software Engineer,
> email: [email protected]
> mobile: +94772596173
>
--
Kathees
Software Engineer,
email: [email protected]
mobile: +94772596173
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
