[
https://issues.apache.org/jira/browse/CAMEL-17512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17482404#comment-17482404
]
James Netherton commented on CAMEL-17512:
-----------------------------------------
I think I tracked down why this issue happens. It only affects JMS endpoints or
any component that extends camel-jms.
Here's where the URI is resolved:
https://github.com/apache/camel/blob/80b92e3624ae5db59a1a24a441f1b10b39eaa1a5/components/camel-jms/src/main/java/org/apache/camel/component/jms/JmsSendDynamicAware.java#L75-L78
The 'replaceFirst' part effectively replaces the dynamic queue name with the
original toD expression. Not sure if this necessary or whether it could just
return entry.getUri().
> Make tracing SpanDecorators work better with toD
> ------------------------------------------------
>
> Key: CAMEL-17512
> URL: https://issues.apache.org/jira/browse/CAMEL-17512
> Project: Camel
> Issue Type: Improvement
> Components: camel-opentelemetry, camel-tracing
> Reporter: James Netherton
> Priority: Minor
>
> Originally reported here:
> https://github.com/apache/camel-quarkus/issues/3461
> If toD is used in routes, then the tracing SpanDecorator does not resolve the
> placeholder values (not sure if it's possible?). So when the recorded spans
> are viewed in a UI, it looks bit weird and confusing because it's not obvious
> where the trace events originated from.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
