[ 
https://issues.apache.org/jira/browse/SYNAPSE-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865530#action_12865530
 ] 

Ruwan Linton commented on SYNAPSE-593:
--------------------------------------

Supun,

This patch violates the proxy service semantics, and introduces a bit of 
complexity into the configuration.

When a user creates a proxy the user expects the message to be mediated via 
inSeqeuence and the response to be mediated via the outSequence. If there is a 
receiving sequence specified in the send mediator in the inSequence the 
functionality violates the above semantic.

I am OK with the idea of receiving sequence in general, but -1 for applying 
this patch. We need to work on this a bit more to get this right so that it 
doesn't conflict the original concepts of synapse.

I will try to modify the implementation when I get some free time, or can you 
propose any changes to make sure there are no conflicts in the semantics.

Thanks,
Ruwan 

> 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]

Reply via email to