[
https://issues.apache.org/activemq/browse/CAMEL-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41267#action_41267
]
Hadrian Zbarcea commented on CAMEL-279:
---------------------------------------
I think Roman's right. The effects of an invocation
{code:java}
beanRef("someBeanName", "someMethodName").
beanRef("someBeanName")
{code}
should not extend beyond its scope. For the second call one should either
explicitly define the method to be invoked or to rely on the request made by
the caller via the METHOD_NAME header. I updated the code to reflect this
behavior.
> 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.
