Diwakar,
We mainly recommend the JBI support in ServiceMix 4.x to quickly enable you to move your application to the new version and then start migrating it to Camel/CXF/... If your application requires a lot of work to deploy it as JBI on ServiceMix 4.x in the first place, I would rather invest that time in migrating to using Camel and OSGi bundles straight away instead. Regards, Gert Vanthienen ------------------------ FuseSource Web: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ On Mon, Jun 11, 2012 at 9:51 AM, diwakar <[email protected]> wrote: > Hi, > > >> Apache ServiceMix 4.x also comes with JBI support ... Almost all > our existing JBI components > are compatible with and available in ServiceMix 4.x > We have many custom SE/BCs and it has to be migrated to 4.x (adding > blueprint.xml etc...). AFAIK the threading model of 4.x is not same as 3.x. > Also JBI support in Servicemix 5.x is not clear (It may not > support). > From forum/web, I understand that not many are migrating to JBI is > Servicemix 4.x (and also few have failed in migrating JBI based code from > 3.x to 4.x). > So we are not sure if it is worth the effort to migrate to JBI in > 4.x. > Please let me know your comment. > > With Best Regards, > Diwakar > > > -- > View this message in context: > http://servicemix.396122.n5.nabble.com/DISCUSS-ServiceMix-3-x-EOL-tp5713318p5713636.html > Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
