Use Camel 2.16 onwards, see http://camel.apache.org/using-camelproxy.html
On Thu, Jan 21, 2016 at 10:26 PM, Ranx <[email protected]> wrote: > I noted that this was closed as "not a problem". I think it is a serious > glitch when the framework isn't respecting something as fundamental as the > contract specified by the interface. > > I'm putting in a Fuse installation for clients right now and showing a bunch > of seasoned Java developers how to use Camel and the framework. To explain > to them that they can't count on the interface acting the way it is expected > to is problematic at best. > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Proxy-BeanInvocations-turning-into-first-class-payloads-tp5724721p5776505.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
