[
https://issues.apache.org/activemq/browse/CAMEL-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41083#action_41083
]
Roman Kalukiewicz commented on CAMEL-279:
-----------------------------------------
Hello Guys!
Didn't we just came back to the very beginning of the issue with the patch that
was applied?
Because now we explicitly set the {{METHOD_NAME}} header in {{BeanProcessor}}
so it affects further invocations and clears the current value of the header
(title of this issue ;) ).
I agree with James that we should use the method name provided, but
{code}
setHeader(METHOD_NAME, constant("bar")
.beanRef("someBeanName", "foo")
.beanRef("someBeanName")
{code}
should result (I think) with {{foo()}} invocation and then {{bar()}} (from
header) while now the header seems to be overridden.
BTW I don't have any access to java on the computer I'm using right now, so it
is hard to test it. If I'm wrong - just ignore it. I'm just looking at the mail
that describes the latest commit.
> BeanProcessor permanently sets METHOD_NAME header
> -------------------------------------------------
>
> Key: CAMEL-279
> URL: https://issues.apache.org/activemq/browse/CAMEL-279
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Reporter: Roman Kalukiewicz
> Assignee: Willem Jiang
> Fix For: 1.3.0
>
> Attachments: bean-processor.patch
>
>
> Issue described here:
> http://www.nabble.com/BeanProcessor-multiple-method-invocation-on-same-bean-to14506245s22882.html#a14506245
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
