[
https://issues.apache.org/jira/browse/CAMEL-11871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16190954#comment-16190954
]
Peter Palaga commented on CAMEL-11871:
--------------------------------------
For the record, why this was actually accepted:
The STOMP spec [1] says
bq. The STOMP protocol treats destinations as opaque string and their syntax is
server implementation specific.
The user knows with which STOMP broker is he speaking, hence the user should
know the proper naming scheme. To the very opposite, the stomp Camel component
has no info which specific stomp implementation is on the other side. Stomp
Camel component can thus make no assumptions about the naming scheme.
[1] https://stomp.github.io/stomp-specification-1.2.html
> Stomp component should not modify the destination name
> ------------------------------------------------------
>
> Key: CAMEL-11871
> URL: https://issues.apache.org/jira/browse/CAMEL-11871
> Project: Camel
> Issue Type: Bug
> Components: camel-stomp
> Reporter: Peter Palaga
> Assignee: Peter Palaga
> Fix For: 2.20.0
>
>
> Stomp Camel Component modifies the destination name passed via endpoint URI
> by prepending a slash to it and by replacing ':' with '/' [1]. This turns out
> to be problematic when targeting an ActiveMQ Artemis instance embedded in
> WildFly. For whatever reason, it expects queue names to start with
> "jms.queue." without the initial slash.
> There is a WildFly Camel integration test demonstrating the issue: [2]
> StompComponent should not assume anything about the naming scheme, because it
> has no control over the decisions made on the broker side.
> [1]
> https://github.com/apache/camel/blob/98b3d7eae9959645c4bc023bf4896d036ce75642/components/camel-stomp/src/main/java/org/apache/camel/component/stomp/StompComponent.java#L57
> [2]
> https://github.com/ppalaga/wildfly-camel/commit/15e3e6098b3976cb057f4208565296ea6bd54017#diff-bf122ce705f9ef0b3920d968d1f13f2a
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
