Hi, maybe another solution to this problem could be to add a kind of descriptor file:
in camel a bean can extract parameters from headers or something else with annotations, if there is a file saying the same thing the bean could not use any camel imports but do the same. what do you think of a file like: <methods> <method class="aaa" method="bbb"> <parameter index="ccc"> <annotation class="ddd"> <annotation-parameter name="eee" value="fff" /> </annotation> </parameter> </method> </methods> - Romain 2011/5/6 Romain Manni-Bucau <rmannibu...@gmail.com>: > Hi, > > i would like to do a route with a bit more bean invocations than > usually and i realise the use of array body to specify parameters is > not very nice, i always have something like: > > from(...).to(<create my array>).to("bean:...").to(<save my output in > headers and replace the body to continue>).... > > do you think it could be improved specifying in the bean component > input/output from headers for example? > > example: > from(...).to("bean:foo.bar.MyClass?method=hello¶meter[0]=header(first)&aprameter[2]=header(other)&result=header(out)").to(...) > > - Romain >