[
https://issues.apache.org/jira/browse/SYNAPSE-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865576#action_12865576
]
Supun Kamburugamuva commented on SYNAPSE-593:
---------------------------------------------
Let me explain my thinking in bit more detail.
What I wanted to say was in Synapse mediation, we have the response receiving
places predefined. For message mediation this place is main sequence and for
proxy services this place is outSequence.
I'm not suggesting to change the existing behavior. I'm simply suggesting to
extend the existing behavior by letting users choose the response receiving
place optionally if they require it (for example for service chaining).
If we look at the current approach for service chaining and the suggested
approach in this Jira, it is pretty clear that the existing approach is very
hard to understand.
I would like to repeat that this is totally optional. Users will use this only
when they require it. So I don't think this optional feature will affect the
existing behavior in any way. rather it will make the synapse configuration
language more powerful.
Thanks,
Supun..
> Specifying a receiving sequence for sent messages
> --------------------------------------------------
>
> Key: SYNAPSE-593
> URL: https://issues.apache.org/jira/browse/SYNAPSE-593
> Project: Synapse
> Issue Type: New Feature
> Components: Core
> Reporter: Supun Kamburugamuva
> Assignee: Supun Kamburugamuva
> Attachments: synapse_service_chaining.patch
>
>
> If a receiving sequence is specified for send mediator, the response can be
> directed to this sequence. This way we can achieve service chaining with
> normal non-blocking transport calls.
> I'm attaching a patch that introduce this feature. Please have a look and
> provide your feed back.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
