You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2024/01/03 17:27:00 UTC
[jira] [Work logged] (ARTEMIS-4488) Support "literal" address setting match
[ https://issues.apache.org/jira/browse/ARTEMIS-4488?focusedWorklogId=897914&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-897914 ]
ASF GitHub Bot logged work on ARTEMIS-4488:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 03/Jan/24 17:26
Start Date: 03/Jan/24 17:26
Worklog Time Spent: 10m
Work Description: jbertram commented on PR #4719:
URL: https://github.com/apache/activemq-artemis/pull/4719#issuecomment-1875717798
This looks good to me, but it needs to be rebased.
Issue Time Tracking
-------------------
Worklog Id: (was: 897914)
Time Spent: 40m (was: 0.5h)
> Support "literal" address setting match
> ---------------------------------------
>
> Key: ARTEMIS-4488
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4488
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> There are use-cases (mainly with MQTT) where wildcard addresses need to be configured differently from the the addresses which actually match the wildcard. Currently we have no way to separate these two categories. We need a new configuration semantic to enable this differentiation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)