Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of clevers594@gmail.com designates
 74.125.82.68 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGB5yN=Otj6FqyQBsUDnmf8AWTN2cghTwk9KrNG0EyYxOpU9Xg@mail.gmail.com>
References: 
 <CACwTa_znLP5q0r4HXZhfE_LsAmRk4rXjZBV1vYn0Rh3ptC5CiA@mail.gmail.com>
	<CAGB5yNkwej_Z9gQCwxBo1N8su5VO978sgCJ3yPHxJ-sFC91BPQ@mail.gmail.com>
	<CACwTa_xGT=gQzYL2UFtt_D-J5fAxKtBtG9x+c_Z-t1yyo0FoYg@mail.gmail.com>
	<F3B95D9661E15E459E329DCDC7529AA428B05F4A@DEWDFEMB16B.global.corp.sap>
	<CAGB5yN=Otj6FqyQBsUDnmf8AWTN2cghTwk9KrNG0EyYxOpU9Xg@mail.gmail.com>
Date: Fri, 2 Aug 2013 17:54:14 +0800
Message-ID: 
 <CACwTa_wJc5xUWHuxJ8Xfeg+b1Ye=8t7G10YF0+TqcPnZREWs=A@mail.gmail.com>
Subject: Re: Compatibility problem from camel 2.10.* (or may be older) to
 2.11.*
From: liugang594 Liu <clevers594@gmail.com>
To: users <users@camel.apache.org>
Content-Type: multipart/alternative; boundary=f46d043c7adcfa56c304e2f3f0db

--f46d043c7adcfa56c304e2f3f0db
Content-Type: text/plain; charset=ISO-8859-1

OK, it's worth to try, thanks.


2013/8/2 Claus Ibsen <claus.ibsen@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.siano@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 <claus.ibsen@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 <clevers594@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

--f46d043c7adcfa56c304e2f3f0db--