[
https://issues.apache.org/jira/browse/CAMEL-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13078883#comment-13078883
]
Claus Ibsen commented on CAMEL-4293:
------------------------------------
I can see your issue as you use @Bean in the method signature, and thus it uses
the method name that was used to invoke itself. That of course is not expected.
However if you do route to a bean, and provide a header with a method name,
then that header is being used.
> @Bean method name is ignored
> ----------------------------
>
> Key: CAMEL-4293
> URL: https://issues.apache.org/jira/browse/CAMEL-4293
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.8.0
> Environment: Win7, Java 1.6_25, Eclipse Helios, m2Eclipse, maven 3.x
> Reporter: Vincent MATHON
> Attachments: camel-bug-2.8.0.zip
>
>
> Since 2.8.0 Exchange.BEAN_METHOD_NAME is always used instead of @Bean method
> name (see BeanInfo.createInvocation(Object pojo, Exchange exchange)). As a
> consequence, the wrong method is choosen when I use a beanref invokation on a
> method that uses @Bean
> parameter binding.
> I built a simple test case as a zip file containing an Eclipse Helios maven
> project (see attachment). The test fails with camel 2.8.0 and succeeds with
> 2.7.3 and earlier (at least until 2.6.0).
> regards
> Vincent MATHON
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
