[
https://issues.apache.org/jira/browse/SYNAPSE-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865554#action_12865554
]
Ruwan Linton commented on SYNAPSE-593:
--------------------------------------
I am sorry, I didn't get you.
What do you mean by predefine, and what does your patch do to change the
behavior of predefining the receiving point, even though the receiving points
for the main sequence is hard coded (is this what you mean by predefined??),
for proxy services it is not. It is a configuration.
We have only one request receiving point for message mediation (if it is not a
proxy), which is main sequence, why do we want to change the receiving point
for response for message mediation.
To me this makes it complex to understand the configuration.
Folks, one of the key advantages of the synapse is its configuration language
and the simplicity of the configuration model, I am not for sacrificing the
simplicity... that is why I don't like making the inlined endpoints to have a
mandatory name as well. (discussed on another thread)
One could argue on the fact that for message chaining scenario it makes it
easy, but it makes it complex to understand the overall design on the message
flow.
> 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]
