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

List:       axis-c-dev
Subject:    [jira] Commented: (AXIS2C-1210) Service Client does not Pick the
From:       "Damitha Kumarage (JIRA)" <jira () apache ! org>
Date:       2008-06-30 12:15:45
Message-ID: 594095840.1214828145124.JavaMail.jira () brutus
[Download RAW message or body]


    [ 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


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