You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Danushka Menikkumbura (JIRA)" <ji...@apache.org> on 2008/06/30 08:21:45 UTC
[jira] Created: (AXIS2C-1210) Service Client does not Pick the
Correct Transport Receiver
Service Client does not Pick the Correct Transport Receiver
-----------------------------------------------------------
Key: AXIS2C-1210
URL: https://issues.apache.org/jira/browse/AXIS2C-1210
Project: Axis2-C
Issue Type: Bug
Components: core/transport
Affects Versions: Current (Nightly)
Reporter: Danushka Menikkumbura
In dual-channel scenarios, the service client (the listener manager) picks the transport receiver based on the value of the service client option, "transport_in_protocol". By default this has the value AXIS2_TRANSPORT_ENUM_HTTP and hence, the listener manager starts an HTTP receiver irrespective of the actual transport receiver unless we specify the transport_in_protocol explicitly using axis2_options_set_transport_in_protocol in the client implementation. But we should keep this setting transparent to the client programmer and ideally we can set this value inside the axis2_options_set_reply_to call because it is possible to infer the transport protocol by looking at the reply-to address.
--
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Commented: (AXIS2C-1210) Service Client does not Pick the
Correct Transport Receiver
Posted by "Damitha Kumarage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609214#action_12609214 ]
Damitha Kumarage commented on AXIS2C-1210:
------------------------------------------
dual channel samples should work for tcp if you specify in the options the transport-in protocol. Also I don't see any wrong in specifying a default transport-in protocol in case user don't specifically set the transport in protocol in the options struct. However your suggestion of inferring transport-in protocol from the reply-to address seems a more elegant approach.
> Service Client does not Pick the Correct Transport Receiver
> -----------------------------------------------------------
>
> Key: AXIS2C-1210
> URL: https://issues.apache.org/jira/browse/AXIS2C-1210
> Project: Axis2-C
> Issue Type: Bug
> Components: core/transport
> Affects Versions: Current (Nightly)
> Reporter: Danushka Menikkumbura
>
> In dual-channel scenarios, the service client (the listener manager) picks the transport receiver based on the value of the service client option, "transport_in_protocol". By default this has the value AXIS2_TRANSPORT_ENUM_HTTP and hence, the listener manager starts an HTTP receiver irrespective of the actual transport receiver unless we specify the transport_in_protocol explicitly using axis2_options_set_transport_in_protocol in the client implementation. But we should keep this setting transparent to the client programmer and ideally we can set this value inside the axis2_options_set_reply_to call because it is possible to infer the transport protocol by looking at the reply-to address.
--
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Commented: (AXIS2C-1210) Service Client does not Pick the
Correct Transport Receiver
Posted by "Supun Kamburugamuva (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609164#action_12609164 ]
Supun Kamburugamuva commented on AXIS2C-1210:
---------------------------------------------
I think this prevents dual channel working with AMQP. I really like to see this fixed before 1.5 since AMQP transport is a major improvement in the new release. Can we do this in a short time period? Thoughts?
> Service Client does not Pick the Correct Transport Receiver
> -----------------------------------------------------------
>
> Key: AXIS2C-1210
> URL: https://issues.apache.org/jira/browse/AXIS2C-1210
> Project: Axis2-C
> Issue Type: Bug
> Components: core/transport
> Affects Versions: Current (Nightly)
> Reporter: Danushka Menikkumbura
>
> In dual-channel scenarios, the service client (the listener manager) picks the transport receiver based on the value of the service client option, "transport_in_protocol". By default this has the value AXIS2_TRANSPORT_ENUM_HTTP and hence, the listener manager starts an HTTP receiver irrespective of the actual transport receiver unless we specify the transport_in_protocol explicitly using axis2_options_set_transport_in_protocol in the client implementation. But we should keep this setting transparent to the client programmer and ideally we can set this value inside the axis2_options_set_reply_to call because it is possible to infer the transport protocol by looking at the reply-to address.
--
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Updated: (AXIS2C-1210) Service Client does not Pick the
Correct Transport Receiver
Posted by "S.Uthaiyashankar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
S.Uthaiyashankar updated AXIS2C-1210:
-------------------------------------
Component/s: core/clientapi
> Service Client does not Pick the Correct Transport Receiver
> -----------------------------------------------------------
>
> Key: AXIS2C-1210
> URL: https://issues.apache.org/jira/browse/AXIS2C-1210
> Project: Axis2-C
> Issue Type: Bug
> Components: core/clientapi, core/transport
> Affects Versions: Current (Nightly)
> Reporter: Danushka Menikkumbura
>
> In dual-channel scenarios, the service client (the listener manager) picks the transport receiver based on the value of the service client option, "transport_in_protocol". By default this has the value AXIS2_TRANSPORT_ENUM_HTTP and hence, the listener manager starts an HTTP receiver irrespective of the actual transport receiver unless we specify the transport_in_protocol explicitly using axis2_options_set_transport_in_protocol in the client implementation. But we should keep this setting transparent to the client programmer and ideally we can set this value inside the axis2_options_set_reply_to call because it is possible to infer the transport protocol by looking at the reply-to address.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AXIS2C-1210) Service Client does not Pick the
Correct Transport Receiver
Posted by "Danushka Menikkumbura (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609167#action_12609167 ]
Danushka Menikkumbura commented on AXIS2C-1210:
-----------------------------------------------
Even TCP dual-channel should not work?
> Service Client does not Pick the Correct Transport Receiver
> -----------------------------------------------------------
>
> Key: AXIS2C-1210
> URL: https://issues.apache.org/jira/browse/AXIS2C-1210
> Project: Axis2-C
> Issue Type: Bug
> Components: core/transport
> Affects Versions: Current (Nightly)
> Reporter: Danushka Menikkumbura
>
> In dual-channel scenarios, the service client (the listener manager) picks the transport receiver based on the value of the service client option, "transport_in_protocol". By default this has the value AXIS2_TRANSPORT_ENUM_HTTP and hence, the listener manager starts an HTTP receiver irrespective of the actual transport receiver unless we specify the transport_in_protocol explicitly using axis2_options_set_transport_in_protocol in the client implementation. But we should keep this setting transparent to the client programmer and ideally we can set this value inside the axis2_options_set_reply_to call because it is possible to infer the transport protocol by looking at the reply-to address.
--
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org