You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Ruwan Linton (JIRA)" <ji...@apache.org> on 2008/04/12 20:13:09 UTC
[jira] Created: (SYNAPSE-269) Fix the dual channel invocation of
synapse as a client
Fix the dual channel invocation of synapse as a client
------------------------------------------------------
Key: SYNAPSE-269
URL: https://issues.apache.org/jira/browse/SYNAPSE-269
Project: Synapse
Issue Type: Bug
Components: Transports
Affects Versions: 1.1.1
Environment: All envs
Reporter: 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-269) Fix the dual channel invocation of
synapse as a client
Posted by "Jens Goldhammer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588378#action_12588378 ]
Jens Goldhammer commented on SYNAPSE-269:
-----------------------------------------
Great stuff to make the configuration within WS-Addressing. Maybe you can give the attribute a better name like "useCallback" or "useTwoWayChannel" instead of "separateListener" (I know it is the name of the method for the options-class....)? I think, this would make it better to undestand it.
Thanks,
Jens
> Fix the dual channel invocation of synapse as a client
> ------------------------------------------------------
>
> Key: SYNAPSE-269
> URL: https://issues.apache.org/jira/browse/SYNAPSE-269
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-269) Fix the dual channel invocation of
synapse as a client
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589078#action_12589078 ]
Ruwan Linton commented on SYNAPSE-269:
--------------------------------------
Now you can configure synapse to invoke the actual service on a dual channel.
> Fix the dual channel invocation of synapse as a client
> ------------------------------------------------------
>
> Key: SYNAPSE-269
> URL: https://issues.apache.org/jira/browse/SYNAPSE-269
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-269) Fix the dual channel invocation of
synapse as a client
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588407#action_12588407 ]
Ruwan Linton commented on SYNAPSE-269:
--------------------------------------
Jens,
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.
Ruwan
> Fix the dual channel invocation of synapse as a client
> ------------------------------------------------------
>
> Key: SYNAPSE-269
> URL: https://issues.apache.org/jira/browse/SYNAPSE-269
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Assigned: (SYNAPSE-269) Fix the dual channel invocation of
synapse as a client
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruwan Linton reassigned SYNAPSE-269:
------------------------------------
Assignee: Ruwan Linton
> Fix the dual channel invocation of synapse as a client
> ------------------------------------------------------
>
> Key: SYNAPSE-269
> URL: https://issues.apache.org/jira/browse/SYNAPSE-269
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Resolved: (SYNAPSE-269) Fix the dual channel invocation of
synapse as a client
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruwan Linton resolved SYNAPSE-269.
----------------------------------
Resolution: Fixed
Fixed on the SVN trunk
> Fix the dual channel invocation of synapse as a client
> ------------------------------------------------------
>
> Key: SYNAPSE-269
> URL: https://issues.apache.org/jira/browse/SYNAPSE-269
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org