camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Kalukiewicz (JIRA)" <>
Subject [jira] Commented: (CAMEL-279) BeanProcessor permanently sets METHOD_NAME header
Date Sun, 20 Jan 2008 10:09:21 GMT


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

setHeader(METHOD_NAME, constant("bar")
.beanRef("someBeanName", "foo")

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

> BeanProcessor permanently sets METHOD_NAME header
> -------------------------------------------------
>                 Key: CAMEL-279
>                 URL:
>             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:

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message