Thanks for answer..
But IMHO it isn't "stream-caching" problem. I have stream-caching enabled by
"camel-context" attribute:
In addition, when I change the route, where I used bean component twice:
I got this result:
2013-10-01 12:26:37.259 DEBUG {main} [SendProcessor]
End
Hello,
I am playing with "bean binding" on bean component. I know, that I can solve my
requirements by another way.
But anyway I think, that my "syntetic" example doesn't work how I expect (I
tested it with Camel 2.11.2, 2.12.1).
I have a "streamBodyBindingBean" bean with this method:
public v
