camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (CAMEL-279) BeanProcessor permanently sets METHOD_NAME header
Date Fri, 18 Jan 2008 09:40:21 GMT

     [ https://issues.apache.org/activemq/browse/CAMEL-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

James Strachan reopened CAMEL-279:
----------------------------------


I was wondering if a neater solution would be that whenever we use code like this...

{code}
beanRef("someBeanName", "someMethodName")
{code}

that we always use that method name - and ignore the header thats on the message. i.e. if
someone really wants a *foo* method to be called in the DSL, we shouldn't magically call some
other method just because there's a header (from maybe a previous message exchange or something).

Thoughts?

> 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.


Mime
View raw message