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 Message----- From: liugang594 Liu [mailto:clevers...@gmail.com] Sent: Freitag, 2. August 2013 09:47 To: users Subject: Re: Compatibility problem from camel 2.10.* (or may be older) to 2.11.* 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 : > > > > 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 compatibility, I'd like to know > Does > > anybody know how to handle this situation ? Thanks. > > > > -- > > Thanks > > GangLiu > > MSN: liugang_0...@hotmail.com > > Skype: gang.liu.talendbj > > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > Email: cib...@redhat.com > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen > -- Thanks GangLiu Mail: clevers...@gmail.com
