[
https://issues.apache.org/jira/browse/CAMEL-5796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499821#comment-13499821
]
Claus Ibsen commented on CAMEL-5796:
------------------------------------
Babak, I suggest you mix our patches. So its the fix from my patch in the core,
and then add your additional unit tests as well. Then we have the optional fix
for this.
> The combination of the transacted DSL together with the <setHeader> or
> <setBody> prohibits to resolve the properties properly.
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-5796
> URL: https://issues.apache.org/jira/browse/CAMEL-5796
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.10.2
> Reporter: Babak Vahdat
> Fix For: 2.9.5, 2.10.3, 2.11.0
>
> Attachments: CAMEL-5796-fix.patch, CAMEL-5796.patch
>
>
> Given the property {{myKey}} defined as:
> {code}
> myKey=myValue
> {code}
> Then consider the following trivial route:
> {code:xml}
> <route>
> <from uri="activemq:queue:okay" />
> <transacted />
> <setHeader headerName="myHeader">
> <constant>{{myKey}}</constant>
> </setHeader>
> <to uri="mock:test" />
> </route>
> {code}
> Because of the usage of the {{transacted}} DSL the property placeholder
> {{{{myKey}}}} will not be resolved to {{myValue}} properly. This behaviour
> would disappear if you would remove the {{transacted}} DSL. And I'm observing
> the same behaviour using the {{setBody}} DSL as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
