[prev in list] [next in list] [prev in thread] [next in thread] 

List:       axis-c-dev
Subject:    [jira] Updated: (AXIS2C-1210) Service Client does not Pick the
From:       "S.Uthaiyashankar (JIRA)" <jira () apache ! org>
Date:       2009-09-08 3:16:57
Message-ID: 1782611573.1252379817491.JavaMail.jira () brutus
[Download RAW message or body]


     [ 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.


[prev in list] [next in list] [prev in thread] [next in thread]