You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by liugang594 Liu <cl...@gmail.com> on 2013/08/02 04:19:59 UTC
Compatibility problem from camel 2.10.* (or may be older) to 2.11.*
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_0011@hotmail.com
Skype: gang.liu.talendbj
Re: Compatibility problem from camel 2.10.* (or may be older) to 2.11.*
Posted by liugang594 Liu <cl...@gmail.com>.
OK, it's worth to try, thanks.
2013/8/2 Claus Ibsen <cl...@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 <st...@sap.com>
> wrote:
> > 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:clevers594@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 <cl...@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 <cl...@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_0011@hotmail.com
> >> > Skype: gang.liu.talendbj
> >>
> >>
> >>
> >> --
> >> Claus Ibsen
> >> -----------------
> >> Red Hat, Inc.
> >> Email: cibsen@redhat.com
> >> Twitter: davsclaus
> >> Blog: http://davsclaus.com
> >> Author of Camel in Action: http://www.manning.com/ibsen
> >>
> >
> >
> >
> > --
> > Thanks
> > GangLiu
> > Mail: clevers594@gmail.com
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> Email: cibsen@redhat.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>
--
Thanks
GangLiu
Mail: clevers594@gmail.com
Re: Compatibility problem from camel 2.10.* (or may be older) to 2.11.*
Posted by Claus Ibsen <cl...@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 <st...@sap.com> wrote:
> 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:clevers594@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 <cl...@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 <cl...@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_0011@hotmail.com
>> > Skype: gang.liu.talendbj
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> Email: cibsen@redhat.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>>
>
>
>
> --
> Thanks
> GangLiu
> Mail: clevers594@gmail.com
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: Compatibility problem from camel 2.10.* (or may be older) to 2.11.*
Posted by liugang594 Liu <cl...@gmail.com>.
Sorry, as my understand, org.apache.camel.spi.Registry should be a public
interface, right? or camel user should never implement it directly? I'm not
sure about it.
2013/8/2 Siano, Stephan <st...@sap.com>
> 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:clevers594@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 <cl...@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 <cl...@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_0011@hotmail.com
> > > Skype: gang.liu.talendbj
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > Red Hat, Inc.
> > Email: cibsen@redhat.com
> > Twitter: davsclaus
> > Blog: http://davsclaus.com
> > Author of Camel in Action: http://www.manning.com/ibsen
> >
>
>
>
> --
> Thanks
> GangLiu
> Mail: clevers594@gmail.com
>
--
Thanks
GangLiu
Mail: clevers594@gmail.com
RE: Compatibility problem from camel 2.10.* (or may be older) to
2.11.*
Posted by "Siano, Stephan" <st...@sap.com>.
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:clevers594@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 <cl...@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 <cl...@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_0011@hotmail.com
> > Skype: gang.liu.talendbj
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> Email: cibsen@redhat.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>
--
Thanks
GangLiu
Mail: clevers594@gmail.com
Re: Compatibility problem from camel 2.10.* (or may be older) to 2.11.*
Posted by liugang594 Liu <cl...@gmail.com>.
if no source code, seems not way to make it work on new version. :(
2013/8/2 Claus Ibsen <cl...@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 <cl...@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_0011@hotmail.com
> > Skype: gang.liu.talendbj
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> Email: cibsen@redhat.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>
--
Thanks
GangLiu
Mail: clevers594@gmail.com
Re: Compatibility problem from camel 2.10.* (or may be older) to 2.11.*
Posted by Claus Ibsen <cl...@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 <cl...@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_0011@hotmail.com
> Skype: gang.liu.talendbj
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen