jBPM 正在消亡吗？ jBPM 和 Activiti BPMN 的未来是什么？
我听说“jBPM”的开发人员最近已经转移到“Activiti BPMN 2”（例如：Tom）。
我想知道对 jBPM 的支持是否会结束。此外，我很高兴听到您的想法，随着时间的推移，Activiti BPMN 的改进是否会使其比 jBPM 更好或更有用？
我也想知道它们之间有什么优点/缺点。
I have heard that the developers of "jBPM" have transferred to "Activiti BPMN 2" in recent times (ex: Tom).
I am wondering about is whether the support for jBPM will be over or not.. Besides, I would be glad to hear your ideas about if the improvements of Activiti BPMN will make it better or useful than jBPM as time goes on?
I would also like to know what are the pros/cons between them.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（9）
历史教训：
jBPM 及其生成的项目：
Activi 的创建者离开 Alfresco 并启动一个新的 BPM 工具 Flowable，它是 Activi 的一个分支。
Camunda 是另一个从 Activi 派生的 BPM 工具。它们还遵守 BPMN 2.0 规范。他们有 Zeebe，这是一个云原生 BPM，带有 Java、gRPC、Elasticsearch 和 Kubernetes 的连接器。
非 jBPM 工作流程/编排工具：
History Lesson:
jBPM and its resultant projects:
Creators of Activi leave Alfresco and start a new BPM tool, Flowable, which is a fork from Activi.
Camunda is another BPM tool forked from Activi. They also adhere to BPMN 2.0 Specification. They have Zeebe, a cloud-native BPM with connectors to Java, gRPC, Elasticsearch and Kubernetes.
Non-jBPM workflow/orchestration tools:
Activiti 是一个有趣的项目，原因如下：
他们打算将引擎商品化。因此，他们使用 Apache 软件许可证。到目前为止，已有多家公司支持该项目。 “商业模式”有点类似于 OpenStack 使用的模式。
拥有一个每个人都可以使用的 BPMN 2.0 引擎是有意义的。这确实包括 jBoss（但我怀疑他们很快就会切换）。
Activiti is an interesting project for several reasons:
They intend to commoditize the engine. For that reason they use the Apache Software License. So far several companies are backing that project. The "business model" is somewhat similar to that used by OpenStack.
It makes sense to have one BPMN 2.0 engine which is used and can be used by everybody. This does include jBoss (but I doubt that they will switch soon).
我撤回了 14 年之前的回答。从今天的角度来看，答案肯定应该包括 jBPM、Activiti、Flowable 和 Camunda。这是人们在寻找重要的基于 BPMN2 标准的开源工作流引擎时最终的选择。
恕我直言，jBPM 仍然非常以 Java 为中心，感觉就像一个由社区构建的老式开源产品，并且仍然缺乏产品管理。
大部分 Activiti 贡献者离开并分叉了 Camunda 和 Flowable。看来 Activiti 的重点是围绕 Alfresco 及其 DMS 的需求。
如果您认为 Google 趋势与答案相关，它目前看起来像这样： https://trends.google.com/trends/explore?q=jBPM,Camunda,Activiti,Flowable
I withdrew my previous answer from '14. From today's perspective the answer should certainly include jBPM, Activiti, Flowable and Camunda. This is the selection one ends up with when looking for the significant BPMN2 standard-based open-source workflow engines.
IMHO, jBPM remains very Java-centric, feels like an old-school open-source product built by a community and still shows a lack of product management.
Major parts of the Activiti contributors lefts and forked Camunda and Flowable. It seems like Activiti's focus is around the needs of Alfresco and their DMS.
If you consider Google trends of relevance to the answer, it currently looks like this: https://trends.google.com/trends/explore?q=jBPM,Camunda,Activiti,Flowable
请查看 jBPM 7：https://www.jbpm.org/learn/releases.html< /a>
对 jBPM 的支持和开发肯定仍在继续！
（顺便说一句，jBPM 也使用 BPMN 2.0）
Please check out jBPM 7: https://www.jbpm.org/learn/releases.html
Support for and development of jBPM is definitely still ongoing!
(Btw, jBPM also uses BPMN 2.0)
jBPM 和 Activiti 都是 BPMN 引擎
但是比较它们
jBPM比Activiti更复杂
与jBPM相比，它真的很容易与Activiti集成
但 jbpm 仍处于开发阶段，所以 Activity 也处于开发阶段
。无论您的要求是什么，jbpm 中都可以提供一切，它是非常好的 BPM，但与 Activity 相比，它有点复杂，而且没有那么富有成效。
因此，如果您尚未决定使用哪个 bpm，我建议您选择 Activity，因为与 Activity 集成任何内容（例如 LDAP 或 Spring）比 JBPM 更容易。
此外，由于社区提供了良好的用户指南和文档，您可以轻松学习 Activity，但对于 JBPM 用户指南和文档来说，两者都没有那么有帮助。此外，开发人员指南也不符合标准。
好吧，球在你的球场上，你必须做出决定。
一切顺利。
检查此链接
http://www.mastertheboss.com/ activiti-bpmn/jbpm-vs-activiti-which-to-choose
jBPM and Activiti Both are BPMN engines
But on Comparing both of them
jBPM is more complex then Activiti
it is really easy to integrate with Activiti as compared to jBPM
but still jbpm is under development phase so is activity
Whatever is your requirement, everything is available in jbpm ,it is very good BPM but as compared to Activity it is bit complex and not so fruitful.
So if you are yet to decide which bpm I would suggest you to go for Activity because integration of anything with Activity say LDAP or Spring is preety easier as compared to JBPM.
Also you can easily learn Activity because of good userguide and documentation provided by community, but in case of JBPM userguide as well as documentation neither are so helpful. Also Developer guide book is also not up to the mark.
Well ball is in your court ,you have to take decision.
All the Best.
chk this Link
http://www.mastertheboss.com/activiti-bpmn/jbpm-vs-activiti-which-to-choose
尽管与 3.x 和 4.x 版本有很大的不同，但 jBPM 肯定不会消亡。在这里，您可以阅读有关 jBPM 和 Activiti 的更多信息
干杯
弗朗西斯科
Well jBPM is surely not dying although there's a strong departure from the 3.x and 4.x releases. here, you can read more about jBPM and Activiti
Cheers
Francesco
据我了解，jBPM 5是drools flow，刚刚重命名。
所以它最初是作为 drools 业务规则引擎的一部分，现在是
jBPM 4 的后继者。所以我认为 jBPM 项目领导转到 activiti 并不重要...
As I understand it, jBPM 5 is drools flow which just got renamed.
So it started as being part of the drools business rules engine,and is now the
successor of jBPM 4. So i dont think it really matters that the jBPM project lead moved to activiti...
jBPM 传统上有一个很大的缺点：可用性。一直非常强大，但最难使用和集成，这是 Activiti 受欢迎和 jBPM 使用率下降的主要原因。
然而，今年随着新版本 6 的推出以及 Wira 平台的发布，jBPM 重新崛起 (http://www.a1.io/a1io_blog/wira-for-jbpm/ ）提供了一个非常好的jBPM执行框架。
jBPM has traditionally had one big drawback; usability. Has always been very powerful, but the hardest to use and integrate with, a major reason in Activiti's popularity and jBPMs decline in usage.
However, this year sees the resurgence of jBPM with the new Version 6 rolled out as well as the release of the Wira platform ( http://www.a1.io/a1io_blog/wira-for-jbpm/ )that provides a really good jBPM execution framework.
不，jBPM 并没有消亡，但最近几天出现了更简单、轻量级的 BPMN 版本，例如 Camunda、Flowable、Activiti 等等。 jBPM 是这场竞赛中的老玩家之一，与其他工具相比，它在创新、新功能、复杂性、部署、支持、稳定性、社区等方面肯定会输掉竞争。 Redhat PAM 也是另一个原因，它可以比当前 BPM 领导者（如 Pega、IBM BPM 等）便宜 10 倍的价格购买。
最重要的是 - jBPM 不会消亡，并将获得支持。
No, jBPM is not dying but more simpler and lightweight versions of BPMN are coming out recent days like Camunda, Flowable, Activiti and list goes on. jBPM is one of the old player in the race and certainly loosing to competition in terms of innovations, new features, complexity, deployment, support, stability, community etc. etc. compared to these other tool. Also redhat PAM is another reason which can be purchased with 10X cheaper price than current BPM leaders like Pega, IBM BPM etc.
Bottom the line - jBPM is not dying and will get support.