[ 
https://issues.apache.org/jira/browse/ARTEMIS-3369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erwin Dondorp updated ARTEMIS-3369:
-----------------------------------
    Description: 
The Artemis CLI variations producer, consumer, browse and transfer, all prepare 
a destination using function {{getDestination}}. However, this function also 
removes a prefix that it was not looking for. It tests for a topic prefix 
(topic://) and then removes any prefix that was present.

It should explicitly test for the 2 prefixes it cares about (topic:// and 
queue://) and then remove only a recognized prefix when it was present.

PR present
  

  was:
The Artemis CLI variations producer, consumer, browse and transfer, all prepare 
a destination using function {{getDestination}}. However, this function also 
removes a prefix that it was not looking for. It tests for a topic prefix 
(topic://) and then removes any prefix that was present.

It should explicitly test for the 2 prefixes it cares about (topic:// and 
queue://) and then remove only a recognized prefix when it was present.

PR will follow...
 


> CLI removes server-side prefixes from a given address
> -----------------------------------------------------
>
>                 Key: ARTEMIS-3369
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3369
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.17.0
>            Reporter: Erwin Dondorp
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The Artemis CLI variations producer, consumer, browse and transfer, all 
> prepare a destination using function {{getDestination}}. However, this 
> function also removes a prefix that it was not looking for. It tests for a 
> topic prefix (topic://) and then removes any prefix that was present.
> It should explicitly test for the 2 prefixes it cares about (topic:// and 
> queue://) and then remove only a recognized prefix when it was present.
> PR present
>   



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to