[
https://issues.apache.org/jira/browse/CAMEL-7893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Lindberg closed CAMEL-7893.
----------------------------------
Resolution: Invalid
Sorry, there is nothing wrong here.
> Logging is showing incorrect information for actual route when using
> CamelJmsDestinationName in a choice clause
> ---------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-7893
> URL: https://issues.apache.org/jira/browse/CAMEL-7893
> Project: Camel
> Issue Type: Bug
> Affects Versions: 2.14.0
> Reporter: Daniel Lindberg
> Priority: Minor
>
> I have a scenario where I need to use CamelJmsDestinationName to perform
> dynamic routing in cases where a specific input parameter has a value, but in
> cases where it doesn't exist, I fall back to a when() / otherwise() logic
> based xpaths on the body of the message.
> Pseudocode:
> {code}
> .choice()
> .when(header("endpoint").isNotNull())
> //Set to dummy, actual queue name will be set by processor
> .to("activemq:queue:dummy")
> .when().xpath("starts-with(/Messages/message/type/text(),'ItemLocation')")
> .to("message.export.itemlocation")
> {code}
> Let's say that my CamelJmsDestinationName has a value of
> message.export.custom. The actual routing does indeed work as expected,
> however when looking at the log, it states that the message was to the route
> as stated by the second when clause, message.export.itemlocation rather than
> message.export.custom
> {code}
> INFO | >>> (ExportMessageFromJmsRoute) choice -->
> activemq://queue:message.export.itemlocation <<<
> {code}
> This can be VERY confusing when debugging your routes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
