Hi Hiranya,
A patch attached to [1] for the documentation update.
[1] https://issues.apache.org/jira/browse/SYNAPSE-973
Thanks.
On Mon, Aug 26, 2013 at 7:58 AM, Isuru Udana wrote:
> Hi Hiranya,
>
> Sure. I will provide a patch for recent Callout mediator configuration
> language changes.
>
>
Hi Hiranya,
Sure. I will provide a patch for recent Callout mediator configuration
language changes.
Thanks.
On Mon, Aug 26, 2013 at 7:54 AM, Hiranya Jayathilaka
wrote:
> Hi Isuru,
>
> Can you also provide a patch for configuration language guide
> (mediators.xml)?
>
> Thanks,
> Hiranya
>
> On
Hi Isuru,
Can you also provide a patch for configuration language guide (mediators.xml)?
Thanks,
Hiranya
On Aug 20, 2013, at 6:25 AM, Isuru Udana wrote:
> Hi Hiranya,
>
> I have attach a patch to [1] with suggested modifications. A sample and an
> integration test is also attached to [2].
>
Hi Hiranya,
I have attach a patch to [1] with suggested modifications. A sample and an
integration test is also attached to [2].
[1] https://issues.apache.org/jira/browse/SYNAPSE-969
[2] https://issues.apache.org/jira/browse/SYNAPSE-970
Thanks.
On Tue, Aug 20, 2013 at 8:14 AM, Isuru Udana wr
On Tue, Aug 20, 2013 at 12:13 AM, Hiranya Jayathilaka
wrote:
> And one more thing.
>
> I noticed that when the callout mediator is configured with an
> endpointKey, the key is resolved only once (at the first message). Try to
> make it so that the mediator will resolve the key on each message. Tha
On Mon, Aug 19, 2013 at 11:21 AM, Isuru Udana wrote:
> Hi Udayanga,
>
> On Mon, Aug 19, 2013 at 7:01 PM, Udayanga Wickramasinghe <
> mastershield2...@gmail.com> wrote:
>
>>
>>
>>
>> On Sun, Aug 18, 2013 at 9:58 AM, Isuru Udana wrote:
>>
>>> Hi All,
>>>
>>> Currently we have following two main pl
And one more thing.
I noticed that when the callout mediator is configured with an endpointKey, the
key is resolved only once (at the first message). Try to make it so that the
mediator will resolve the key on each message. That way the callout mediator
can take advantage of the underlying cac
Hi Udayanga,
On Mon, Aug 19, 2013 at 7:01 PM, Udayanga Wickramasinghe <
mastershield2...@gmail.com> wrote:
>
>
>
> On Sun, Aug 18, 2013 at 9:58 AM, Isuru Udana wrote:
>
>> Hi All,
>>
>> Currently we have following two main places we use a blocking client to
>> invoke services.
>> 1. Callout Medi
On Sun, Aug 18, 2013 at 9:58 AM, Isuru Udana wrote:
> Hi All,
>
> Currently we have following two main places we use a blocking client to
> invoke services.
> 1. Callout Mediator
> 2. Forwarding Message Processor
>
> Both these components use the axis2 service client to invoke services in a
> blo
_433.xml
> New Blocking Sender implementation
> --
>
> Key: SYNAPSE-966
> URL: https://issues.apache.org/jira/browse/SYNAPSE-966
> Project: Synapse
> Issue Type: New Feature
>
Hi Hiranya,
On Mon, Aug 19, 2013 at 8:08 AM, Hiranya Jayathilaka
wrote:
> Hi Isuru,
>
> I have checked in the patches with a few minor changes. Could you also
> provide a patch for the forwarding message processor?
>
Thanks for committing the patches. I will provide a patch for forwarding
message
Hi Isuru,
I have checked in the patches with a few minor changes. Could you also provide
a patch for the forwarding message processor?
Also, can you extend the callout mediator so that it supports anonymous
(inline) endpoint definitions like the send mediator? I think you already have
all the
. Thanks Isuru for the contribution.
> New Blocking Sender implementation
> --
>
> Key: SYNAPSE-966
> URL: https://issues.apache.org/jira/browse/SYNAPSE-966
> Project: Synapse
> Is
Hi All,
Currently we have following two main places we use a blocking client to
invoke services.
1. Callout Mediator
2. Forwarding Message Processor
Both these components use the axis2 service client to invoke services in a
blocking manner.
Since the implementation is very simple, provided functi
was (Author: isudana):
Please find this improvement from the attachment.
I have added a new axis2.xml (axis2_blocking_client.xml) instead of using the
usual blocking client axis2.xml which is placed in samples directory is not the
ideal place to have it.
> New Blocking
attachment.
I have added a new axis2.xml (axis2_blocking_client.xml) instead of using the
usual blocking client axis2.xml which is placed in samples directory is not the
ideal place to have it.
> New Blocking Sender implementat
Isuru Udana Loku Narangoda created SYNAPSE-966:
--
Summary: New Blocking Sender implementation
Key: SYNAPSE-966
URL: https://issues.apache.org/jira/browse/SYNAPSE-966
Project: Synapse
17 matches
Mail list logo