Uploaded image for project: 'Axis2-C'
  1. Axis2-C
  2. AXIS2C-1210

Service Client does not Pick the Correct Transport Receiver

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None

    Description

      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.

      Attachments

        Activity

          People

            Unassigned Unassigned
            danushka Danushka Menikkumbura
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated: