Hi
Minor migration can be expected when doing Camel upgrades between
minor versions. We list what you need to be aware of in the release
notes.
However a patch release shouldn't have any migration effort. Unless
due to security reasons causing that.
On Mon, Dec 7, 2015 at 6:56 PM, Jérémie wro
thanks for your answer, even if i am a bit disappointed by it. Breaking
existing application isn't good, and the actual behavior seem counter
intuitive : if i forget only one annotation on an interface, i don't have
any warning, but the proxy become invalid.
Moreover, the "binding" attribute didn'
That is how it is now, so set the switch
On Mon, Dec 7, 2015 at 5:53 PM, Jérémie wrote:
> Hello,
>
> I'm in the process to convert an application from Camel 2.14 to Camel 2.16,
> and i have a major regression with Spring Proxy. If i create a proxy with
> spring to an interface with only one metho
Hello,
I'm in the process to convert an application from Camel 2.14 to Camel 2.16,
and i have a major regression with Spring Proxy. If i create a proxy with
spring to an interface with only one method, but several arguments, then
only the last argument is send to the route, and the receiver fail t
