On Tue, Dec 21, 2010 at 10:39 AM, Claus Ibsen wrote:
> You are aware that you do NOT have any MY_ID header when you invoke
> the logStart method on the bean, since the message has just been
> consumed from a file. Therefore it only contains the CamelFileName
> header.
>
> Camel is then not able to
You are aware that you do NOT have any MY_ID header when you invoke
the logStart method on the bean, since the message has just been
consumed from a file. Therefore it only contains the CamelFileName
header.
Camel is then not able to map this header.
On Sun, Dec 19, 2010 at 11:00 PM, Craig Taylo
I've gotten around the problem by turning it into a processor but the route
was pro grammatically generated as
from( "file:/home/myuser/data/in")
.to( "bean:myLogger?method=logStart" )
.process( processor1 )
.to( "bean:myLogger?method=logEnd" );
I'll try and come up with an isolated test
Can you post Camel version used and the route you are using?
On Fri, Dec 17, 2010 at 6:42 PM, Craig Taylor wrote:
> I'm attempting to fire a bean method "logStart" and am receiving a
> conversion error as it appears it's treating my initial integer parameter as
> the body. From trace logs:
>
>
I'm attempting to fire a bean method "logStart" and am receiving a
conversion error as it appears it's treating my initial integer parameter as
the body. From trace logs:
12:33:17,297 | TRACE | tenerContainer-1 | BeanInfo |
he.camel.component.bean.BeanInfo 296 | Creating
