You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2017/07/28 08:58:00 UTC
[jira] [Updated] (QPID-7868) [Java Broker] Allow specifying routing
key when publishing messages via REST
[ https://issues.apache.org/jira/browse/QPID-7868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-7868:
-----------------------------
Fix Version/s: Future
> [Java Broker] Allow specifying routing key when publishing messages via REST
> ----------------------------------------------------------------------------
>
> Key: QPID-7868
> URL: https://issues.apache.org/jira/browse/QPID-7868
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Lorenz Quack
> Fix For: Future
>
>
> Currently, when publishing messages via REST ({{QueueManagingVirtualHost#publishMessage}}) you cannot specify a routing key. The common address pattern "<exchange>/<routingKey>" is not respected.
> Related to this: We should persist the exchange and routing key of InternalMessages in the store. Unfortunately, the MessageMetaData is not versioned making alterations to the stored format very difficult.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org