camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-4115) camel-bean - We ought to remove the CamelBeanMethodName header after usage as its only typically meant for the invoked bean only
Date Fri, 17 Jun 2011 08:44:47 GMT

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

Claus Ibsen resolved CAMEL-4115.
--------------------------------

    Resolution: Fixed

> camel-bean - We ought to remove the CamelBeanMethodName header after usage as its only
typically meant for the invoked bean only
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-4115
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4115
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.8.0
>
>
> See post
> http://urgoringo.wordpress.com/2011/06/17/interesting-behaviour-in-apache-camel-bean-invocation/
> Like we do in eg camel-cache and other components, we remove some of the control headers
for the component (eg CamelCacheOperation) as it was only intended for this invocated bean
only, and not any preceding beans.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message