You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2008/10/20 17:53:44 UTC

[jira] Created: (QPID-1376) [0-8] Client is unable to set the ReplyTo field on a message

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

                 Key: QPID-1376
                 URL: https://issues.apache.org/jira/browse/QPID-1376
             Project: Qpid
          Issue Type: Bug
          Components: Dot Net Client, Starter
    Affects Versions: M3, M4
            Reporter: Martin Ritchie


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. 


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.