[
https://issues.apache.org/jira/browse/QPID-7602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16147012#comment-16147012
]
ASF subversion and git services commented on QPID-7602:
-------------------------------------------------------
Commit aefd3e9a231cd0015d5d65e63fd7f2f113eba2fb in qpid-broker-j's branch
refs/heads/master from [~lorenz.quack]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=aefd3e9 ]
QPID-7602: [Java Broker] Convert reply-to from internal format into AMQP 0-x
> Message reply-to conversion between protocols for point to point and publish
> subscribe messaging patterns
> ---------------------------------------------------------------------------------------------------------
>
> Key: QPID-7602
> URL: https://issues.apache.org/jira/browse/QPID-7602
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
> Fix For: qpid-java-broker-7.0.0
>
>
> When the Java Broker converts a message from one AMQP protocol to another, it
> should strive to retain fidelity of the reply-to header. For example if I
> publish a request message from application using AMQP 0.9 with a reply to a
> response queue, a server application using AMQP 1.0 ought to be able to
> handle request and send a response to to that queue.
> To do this, the Broker's conversion layer is going to need to be sufficiently
> smart to convert, if it can, from one address format to another. This task
> will be complicated by the fact that that the legacy client supported two
> addressing: ADDR and BURL.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
