Qpid
  1. Qpid
  2. QPID-1376

[0-8] Client is unable to set the ReplyTo field on a message

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: M3, M4
    • Fix Version/s: None
    • Component/s: Dot Net Client
    • Labels:

      Description

      Summary:

      Due to the fact that the client code does not have the notion of a destination with which it can set the replyTo in a single method call two calls are required:

      ReplyToExchangeName
      ReplyToRoutingKey

      Must both be set.

      However the client attempts to retrieve the existing ReplyTo to update with either the new ExchangeName or RoutingKey and attempting to create the BindingURL with a null value (as this is a new message) it throws the exception seen in QPID-1375.

      Simply ignoring the null value is not sufficient as after updating the ExchangeName or RoutingKey in the empty BindingURL it attempts to validate it which as it is only partially complete fails.

      We need to think what we want to do here. Perhaps looking at the new 0-10 client to see what it does in this space.

        Activity

        Hide
        Robbie Gemmell added a comment -

        Closing thess issues out as they relate to the old 0-8 and 0-10 .Net clients which were removed from the repository months ago, and not the current .Net bindings for the C++ messaging API.

        Show
        Robbie Gemmell added a comment - Closing thess issues out as they relate to the old 0-8 and 0-10 .Net clients which were removed from the repository months ago, and not the current .Net bindings for the C++ messaging API.

          People

          • Assignee:
            Unassigned
            Reporter:
            Martin Ritchie
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development