JBI死了吗？它仍然是 ESB 选择的有效标准吗？
JBI 标准（曾经？）应该是企业服务总线的标准，特别是在重用/交换不同 ESB（或孤独的服务引擎提供商）功能的设施方面
已知的 JBI 实现是（根据维基百科）：
- OpenESB = > JBI + OSGI（自从 Oracle 收购 Sun 以来，它现在只是社区）
- Petals
- ServiceMix =>最后 (4) 版本基于 OSGI（但仍与 JBI 兼容）
- Fuse =>根据 Guillaume Nodet 的说法，JBI 1.0 和 2.0 已经死亡 http://servicemix.396122.n5.nabble.com/DISCUSS-ServiceMix-future-td3212177.html 关于 WS-Security 的最后一次熔断网络广播使用的是 CXF-Osgi
- Mule =>根据 Ross Mason 的说法，JBI 1.0 已死 http://www.infoq.com /news/2008/05/jbi-debate
- Oracle =>应该是JBI吧？最终遵循 SCA
- TIBCO =>应该是JBI吧？最终遵循 SCA
非实施者：
- IBM =>据我所知不是JBI。最终遵循 SCA
- JBoss =>自定义
如果不考虑 JBI 的工作原理以及它解决的问题与 SCA 不同，您在选择 ESB 时是否真的会考虑它是否符合 JBI 的事实？还是坚持 ESB 的功能？
JBI standard is (was?) supposed to be the standard for Entreprise Service Bus, especially in terms of facility of reuse/exchange of capabilities of different ESBs (or lonely Service Engine providers)
Known JBI implementations are (according to wikipedia) :
- OpenESB => JBI + OSGI (since Oracle bought Sun it is now community only)
- Petals
- ServiceMix => The last (4) release is based on OSGI (but remains compatible with JBI)
- Fuse => According to Guillaume Nodet JBI 1.0 and 2.0 are dead http://servicemix.396122.n5.nabble.com/DISCUSS-ServiceMix-future-td3212177.html Last fuse webcast regarding WS-Security were using CXF-Osgi
- Mule => According to Ross Mason, JBI 1.0 is dead http://www.infoq.com/news/2008/05/jbi-debate
- Oracle => Supposed to be JBI ? Definitively follows SCA
- TIBCO => Supposed to be JBI ? Definitively follows SCA
Non implementers:
- IBM => as far as I know is not JBI. Definitively follows SCA
- JBoss => Custom
Without taking into consideration that JBI works, and that it address different problems than SCA, would you really took into account in an ESB choice the fact that it is or not JBI compliant ? or stick to the capabilities of the ESB ?
Reference: What are the differences / similarities between JBI and SCA
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
是的，jbi快要死了。不会有 jbi 2 规范。查看 jbi 和 servicemix 负责人 gnodet 在他的博客上发布的博客文章，了解他对 jbi 的想法。
与 jbi 相比，进行 apache Camel 或 Spring 集成要容易得多。
Yeah jbi is dying. There is not gonna be a jbi 2 spec. Check out the blog post by gnodet, lead on jbi and servicemix, posted on his blog, about his thoughts on jbi.
Its just so so much easier to do apache camel, or spring integration than jbi.
JBI 的替代方案似乎不止一个......条款中提到的 Apache Camel 或 Spring Integration ..这意味着，JBI 需要作为标准存在..以避免做同一件事的多种方法..
我认为 JBI 将继续进化，因为它只是一个规范而不是实现。Camel 和 Spring 可以遵守这样的规范
更多内容可以阅读
http://www.pymma.com/index.php?option=com_content&view=article&id=127:is-jbi-dead-not-of-course& ;catid=82:blog-paul-perez&Itemid=574
拉贾·纳根德拉·库马尔，
首席技术官
www.tejasoft.com
Alternative to JBI seems to be more than one... Apache Camel or Spring Integration as mentioned by Clause.. which means, JBI need exists as standard.. to avoid multiple ways of doing the same thing..
I think JBI would continue to evolve as it is just a specification and not implementation.. Camel and Spring could comply to such specification
More can be read at
http://www.pymma.com/index.php?option=com_content&view=article&id=127:is-jbi-dead-not-of-course&catid=82:blog-paul-perez&Itemid=574
Raja Nagendra Kumar,
C.T.O
www.tejasoft.com