Hi Diwakar,
IMHO, more than maintaining SMX3, I would work to migrate from JBI to
Camel. Camel components are easy to write and so, it should be quite
easy to migrate your custom JBI components to Camel.
Regards
JB
On 06/11/2012 09:51 AM, diwakar 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.
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
