Oliver,
In ServiceMix 5, we won't be including the JBI and NMR layers nor the JBI components any more. You can still install the older versions of those bundles into ServiceMix 5, but that will only be a convenient solution as long the version ranges of those bundles still match up with what we have available (e.g. for things like Spring, Blueprint, ...). At this moment, we are using our ServiceMix 4 features/trunk to work towards newer 4.5.x releases but we haven't been doing any upgrades to newer versions of Camel, Karaf, ActiveMQ, ... there. We can easily change that and set up the necessary branch to maintain a newer version of ServiceMix 4.x if you or anyone else in the community fancies working on that. In the long run, you'll probably want to move away from JBI for your own development. If you run into any issues or features that are missing or have any tips and tricks to share with other users, we'd obviously be very interested in learning about those experiences too. Regards, Gert Vanthienen On Mon, Apr 29, 2013 at 1:49 PM, Oliver Kuntze <[email protected]> wrote: > Hi Gert, > > what does "remove everything that's related to JBI and the NMR" mean? > > Does it mean that you'll drop further development of the corresponding > bundles but one could use the "old" bundles in Servicemix 5? > Or does it mean that one cannot use existing JBI components in Servicemix 5? > > We have quite some JBI components swimming in our current Servicemix > installation and I'll have to make up my mind regarding migration scenarios. > > Thanks in advance for your insight! > > Best regards > Oliver > > > > > > -- > View this message in context: > http://servicemix.396122.n5.nabble.com/PROPOSAL-New-plan-for-Apache-ServiceMix-5-0-tp5715705p5716603.html > Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
