[
https://issues.apache.org/jira/browse/ARTEMIS-5942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18064318#comment-18064318
]
Justin Bertram commented on ARTEMIS-5942:
-----------------------------------------
The escaping is a result of the translation from the [OpenWire wildcard
syntax|https://activemq.apache.org/components/classic/documentation/wildcards]
to the Core wildcard syntax. Since you're using a character defined in the Core
wildcard syntax in an OpenWire destination then that character is escaped so
that it is not mistaken as part of the the Core wildcard syntax.
> NMS based client causes weird escaping in names
> -----------------------------------------------
>
> Key: ARTEMIS-5942
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5942
> Project: Artemis
> Issue Type: Bug
> Components: Broker, JMS, Management
> Affects Versions: 2.44.0
> Reporter: arne anka
> Priority: Major
>
> My queues/addresses are named with underscores (say, EXP_FOO or IMP_BAR).
> Queues and addresses are set to auto-create and:
> {code:xml}
> <wildcard-addresses>
> <delimiter>_</delimiter>
> </wildcard-addresses>{code}
> This works well.
> Recently I got a client that is implemented using Apache NMS, when that
> client sends/reads from a destination {{NEW_CLIENT}}, in Artemis that name
> appears as
> {noformat}
> NEW\\_CLIENT{noformat}
> Quoting in single quotes results in even more slashes, double quotes in even
> a node (JMX view) \ with child NEW\\_CLIENT\""
> Some research suggested adding
> {noformat}
> <routing-enabled>false</routing-enabled>{noformat}
> to:
> {noformat}
> <wildcard-addresses>{noformat}
> but that didn't help either.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
