Just add the new methods to the registry implementation and it works
in both 2.10 and 2.11.
On Fri, Aug 2, 2013 at 4:19 AM, liugang594 Liu clevers...@gmail.com wrote:
Hi :
I saw the interface org.apache.camel.spi.Registry has significant changes
from 2.10.* to 2.11.* ,
which lead us some
if no source code, seems not way to make it work on new version. :(
2013/8/2 Claus Ibsen claus.ib...@gmail.com
Just add the new methods to the registry implementation and it works
in both 2.10 and 2.11.
On Fri, Aug 2, 2013 at 4:19 AM, liugang594 Liu clevers...@gmail.com
wrote:
Hi :
You have a component that implements an internal camel interface, but you don't
have the source code for it? In that case for an update you need to make the
person who does have the source code make these changes (otherwise you will be
locked in to Camel 2.10 forever)...
-Original
You can use an adapter for the new version if you have the source
code, and adapt from the old api to the new api.
On Fri, Aug 2, 2013 at 10:53 AM, Siano, Stephan stephan.si...@sap.com wrote:
You have a component that implements an internal camel interface, but you
don't have the source code
OK, it's worth to try, thanks.
2013/8/2 Claus Ibsen claus.ib...@gmail.com
You can use an adapter for the new version if you have the source
code, and adapt from the old api to the new api.
On Fri, Aug 2, 2013 at 10:53 AM, Siano, Stephan stephan.si...@sap.com
wrote:
You have a component
Hi :
I saw the interface org.apache.camel.spi.Registry has significant changes
from 2.10.* to 2.11.* ,
which lead us some compatibility problem when changing the camel version to
latest version (we defined some customized Registry implementation inside).
Even it seems no way to keep downward
