Dear Team,
I have a problem with implementing service chaining pattern in ESB and below is
the way I did.
1. Created an API with InSequence and OutSequence
2. In InSequence, using send mediator to invoke and end point and send
had receive attribute to invoke another sequence
>>>
>>>>> +1
>>>>>
>>>>> Looks good to me but can we please change the 'receivingSequence'
>>>>> attribute to something more appropriate? How about 'responseSequence'?
>>>>> Also
>>>
Supun Kamburugamuva wrote:
>>
>>> On Mon, Nov 9, 2009 at 1:27 PM, Hiranya Jayathilaka <
>>> hiranya...@gmail.com> wrote:
>>>
>>>> +1
>>>>
>>>> Looks good to me but can we please change the 'receivingSequence'
>>>&
>
>>> Looks good to me but can we please change the 'receivingSequence'
>>> attribute to something more appropriate? How about 'responseSequence'? Also
>>> I think this feature can be further generalized without restricting it as a
>>> service chaini
t;
>> Looks good to me but can we please change the 'receivingSequence'
>> attribute to something more appropriate? How about 'responseSequence'? Also
>> I think this feature can be further generalized without restricting it as a
>> service chaining featu
on? - could it
>>> become similar to the existing approach?
>>>
>>> Thanks
>>> Indika
>>>
>>> On Mon, Nov 9, 2009 at 11:45 AM, Supun Kamburugamuva
>>> wrote:
>>> > Hi Indika,
>>> >
>>> > Thanks for
+1
Looks good to me but can we please change the 'receivingSequence' attribute
to something more appropriate? How about 'responseSequence'? Also I think
this feature can be further generalized without restricting it as a service
chaining feature. With this feature we can
Hm... Now I can see that new approach has improved usability. I like
this as another option for the service chaining. Let's wait for
suggestions from others.
Thanks
Indika
On Mon, Nov 9, 2009 at 12:56 PM, Supun Kamburugamuva wrote:
> Hi
>
> Sugg
be very difficult to
> > implement in some cases. But with my approach the Synapse configuration
> > become logical and easy.
> >
> > Thanks,
> > Supun..
> >
> > On Mon, Nov 9, 2009 at 10:39 AM, indika kumara
> > wrote:
> >>
> >> Spun we
o implement and maintain. Or it can be very difficult to
> implement in some cases. But with my approach the Synapse configuration
> become logical and easy.
>
> Thanks,
> Supun..
>
> On Mon, Nov 9, 2009 at 10:39 AM, indika kumara
> wrote:
>>
>> Spun we can do the
configuration
become logical and easy.
Thanks,
Supun..
On Mon, Nov 9, 2009 at 10:39 AM, indika kumara wrote:
> Spun we can do the service chaining with synapse . one resource is [1]
> which does the message chaining with a proxy service. You should be
> able to do same thing even with the main
> And... +1 For keeping and retrieving non string properties.
>
Above idea have came form Andreas sometime back [1] (a comment in the JIRA)
[1] https://issues.apache.org/jira/browse/SYNAPSE-503
-
To unsubscribe, e-mail: dev-uns
Spun we can do the service chaining with synapse . one resource is [1]
which does the message chaining with a proxy service. You should be
able to do same thing even with the main sequence (put response true
property and call the new service endpoint within the out mediator).
Could you please
to sequence 1) > sequence 1 (do some
transformations), send (response to sequence 2) > sequence 2, send
the response back.
Just having this functionality does not complete the whole service chaining
requirements. We need a way to store the request and responses and access
the
14 matches
Mail list logo
