[
https://issues.apache.org/jira/browse/CAMEL-5796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499788#comment-13499788
]
Claus Ibsen commented on CAMEL-5796:
------------------------------------
The patch is a good attempt in the correct file to fix this issue. Though as
you have noticed it worked fine without the transacted policy.
The issue is that when you use transacted/policy, it wraps the outputs, and
then its a bit different logic that creates the child processors, than if the
transacted was not there. And that part of the code was missing logic that
pre-prepares the definitions before the processors is created.
I am attaching a better patch with this fix.
Also we can have unit test in camel-core, as you can use policy instead of
transacted. They are the same.
> 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
> 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
