synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ruwan Linton (JIRA)" <>
Subject [jira] Commented: (SYNAPSE-269) Fix the dual channel invocation of synapse as a client
Date Sun, 13 Apr 2008 17:49:05 GMT


Ruwan Linton commented on SYNAPSE-269:


I agree, but this configuration is already there from the 1.0 version, even though this was
not working after the 1.1 release. So I would stick to the above configuration (separateListener="true")
in-order to keep the backward compatibility of the configuration.   


> Fix the dual channel invocation of synapse as a client
> ------------------------------------------------------
>                 Key: SYNAPSE-269
>                 URL:
>             Project: Synapse
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 1.1.1
>         Environment: All envs
>            Reporter: Ruwan Linton
>            Assignee: Ruwan Linton
>             Fix For: 1.2
> Synapse should properly support the dual channel invocation when executing as a client
(i.e. when synapse invokes an actual service to get the response for a mediated request).
> To support this the configuration has to specify this to the engine which can be done
by using the <enableAddressing separateListener="true"/> tag and need to fix the functionality.

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:
For additional commands, e-mail:

View raw message